Re: dump -L

2007-08-18 Thread Victor Sudakov
Vince wrote: > > > >Right now I am watching a dump: > > > >[EMAIL PROTECTED] ~] dump -b64 -5Lau /home > > DUMP: Connection to big.sibptus.tomsk.ru established. > > DUMP: Date of this level 5 dump: Sat Aug 18 14:02:16 2007 > > DUMP: Date of last level 0 dump: Sun Aug 12 11:10:56 2007 > > DUMP: D

Re: dump -L

2007-08-18 Thread Vince
Victor Sudakov wrote: Colleagues, Right now I am watching a dump: [EMAIL PROTECTED] ~] dump -b64 -5Lau /home DUMP: Connection to big.sibptus.tomsk.ru established. DUMP: Date of this level 5 dump: Sat Aug 18 14:02:16 2007 DUMP: Date of last level 0 dump: Sun Aug 12 11:10:56 2007 DUMP: Du

Re: dump -L

2007-08-18 Thread Victor Sudakov
Colleagues, Right now I am watching a dump: [EMAIL PROTECTED] ~] dump -b64 -5Lau /home DUMP: Connection to big.sibptus.tomsk.ru established. DUMP: Date of this level 5 dump: Sat Aug 18 14:02:16 2007 DUMP: Date of last level 0 dump: Sun Aug 12 11:10:56 2007 DUMP: Dumping snapshot of /dev/a

Re: dump -L

2007-08-07 Thread Wojciech Puchar
"expected next file 12345, got 23456" I'm seeing this too. It's always exactly one inode per file system. not one, sometimes even tens. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To uns

Re: dump -L

2007-08-07 Thread Wojciech Puchar
I always use "dump -L" to dump a live filesystem. However, when I restore the dump, I sometimes get messages like "foo.txt (inode 12345) not found on tape" or "expected next file 12345, got 23456" i had it too, sometimes even restore is unable to restore well -1-

Re: dump -L

2007-08-07 Thread [EMAIL PROTECTED]
On 07/08/07, Victor Sudakov <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > > > > > > > Does nobody know the answer, or am I the only one experiencing the > > > > > > > problem? > > > > > > > > > > > > I don't know the answer, but I get essentially the > > > > > > same behaviour. I hav

Re: dump -L

2007-08-07 Thread Victor Sudakov
[EMAIL PROTECTED] wrote: > > > > > > > Does nobody know the answer, or am I the only one experiencing the > > > > > > problem? > > > > > > > > > > I don't know the answer, but I get essentially the > > > > > same behaviour. I have never seen any data loss, > > > > > > > > I gave an example below.

Re: dump -L

2007-08-07 Thread [EMAIL PROTECTED]
On 06/08/07, Victor Sudakov <[EMAIL PROTECTED]> wrote: > > > > > Does nobody know the answer, or am I the only one experiencing the > > > > > problem? > > > > > > > > I don't know the answer, but I get essentially the > > > > same behaviour. I have never seen any data loss, > > > > > > I gave an

Re: dump -L

2007-08-06 Thread Victor Sudakov
cpghost wrote: > > > > > I always use "dump -L" to dump a live filesystem. > > > > > However, when I restore the dump, I sometimes get messages like > > > > > "foo.txt (inode 12345) not found on tape" or > > > > >

Re: dump -L

2007-08-06 Thread Victor Sudakov
Jerry McAllister wrote: > > > Victor Sudakov wrote: > > > > > > I always use "dump -L" to dump a live filesystem. > > > However, when I restore the dump, I sometimes get messages like > > > "foo.txt (inode 12345) not found on tape&quo

Re: dump -L

2007-08-06 Thread Victor Sudakov
Bill Moran wrote: > > > Here is another example: > > > > > > [EMAIL PROTECTED] ~] restore -b64 -rN > > > ./spool/samba.lock/wins.dat: (inode 2829098) not found on tape > > > expected next file 267, got 4 > > > expected next file 2828988, got 2828987 [dd] > > My guess would be that something is

Re: dump -L

2007-08-06 Thread Bill Moran
In response to Jerry McAllister <[EMAIL PROTECTED]>: > On Mon, Aug 06, 2007 at 09:56:15AM +0700, Victor Sudakov wrote: > > > Victor Sudakov wrote: > > > > > > I always use "dump -L" to dump a live filesystem. > > > However, when I restore

Re: dump -L

2007-08-06 Thread Jerry McAllister
On Mon, Aug 06, 2007 at 09:56:15AM +0700, Victor Sudakov wrote: > Victor Sudakov wrote: > > > > I always use "dump -L" to dump a live filesystem. > > However, when I restore the dump, I sometimes get messages like > > "foo.txt (inode 12345) not found

Re: dump -L

2007-08-06 Thread cpghost
On Mon, Aug 06, 2007 at 02:18:57PM +0700, Victor Sudakov wrote: > > > > I always use "dump -L" to dump a live filesystem. > > > > However, when I restore the dump, I sometimes get messages like > > > > "foo.txt (inode 12345) not found on ta

Re: dump -L

2007-08-06 Thread Victor Sudakov
[EMAIL PROTECTED] wrote: > > > > > > I always use "dump -L" to dump a live filesystem. > > > However, when I restore the dump, I sometimes get messages like > > > "foo.txt (inode 12345) not found on tape" or > > > "expected

Re: dump -L

2007-08-05 Thread [EMAIL PROTECTED]
On 05/08/07, Victor Sudakov <[EMAIL PROTECTED]> wrote: > Victor Sudakov wrote: > > > > I always use "dump -L" to dump a live filesystem. > > However, when I restore the dump, I sometimes get messages like > > "foo.txt (inode 12345) not found on t

Re: dump -L

2007-08-05 Thread Victor Sudakov
Victor Sudakov wrote: > > I always use "dump -L" to dump a live filesystem. > However, when I restore the dump, I sometimes get messages like > "foo.txt (inode 12345) not found on tape" or > "expected next file 12345, got 23456" > > I thought

Re: dump -L

2007-07-24 Thread Victor Sudakov
Lowell Gilbert wrote: > >> > What is it? > >> > >> I don't know. Perhaps it is the inode of the snapshot file > >> itself? > > > > "find -inum" does not support this assumtion. > > Do you mean that you can't find the file at all in the snapshot? Here is an example for you: $ restore -rNf test.

Re: dump -L

2007-07-24 Thread Victor Sudakov
Lowell Gilbert wrote: > >> > > >> > I always use "dump -L" to dump a live filesystem. > >> > However, when I restore the dump, I sometimes get messages like > >> > "foo.txt (inode 12345) not found on tape" or > >>

Re: dump -L

2007-07-24 Thread Lowell Gilbert
Victor Sudakov <[EMAIL PROTECTED]> writes: > cpghost wrote: >> > >> > I always use "dump -L" to dump a live filesystem. >> > However, when I restore the dump, I sometimes get messages like >> > "foo.txt (inode 12345) not found on tap

Re: dump -L

2007-07-24 Thread Victor Sudakov
cpghost wrote: > > > > I always use "dump -L" to dump a live filesystem. > > However, when I restore the dump, I sometimes get messages like > > "foo.txt (inode 12345) not found on tape" or > > "expected next file 12345, got 23456"

Re: dump -L

2007-07-24 Thread cpghost
On Tue, Jul 24, 2007 at 06:54:01PM +0700, Victor Sudakov wrote: > Colleagues, > > I always use "dump -L" to dump a live filesystem. > However, when I restore the dump, I sometimes get messages like > "foo.txt (inode 12345) not found on tape" or > "

dump -L

2007-07-24 Thread Victor Sudakov
Colleagues, I always use "dump -L" to dump a live filesystem. However, when I restore the dump, I sometimes get messages like "foo.txt (inode 12345) not found on tape" or "expected next file 12345, got 23456" I thought this should _never_ happen when dumping a sna

"dump -L " not working as expected?

2005-10-09 Thread Victor Sudakov
Colleagues, I dump an active filesystem on a FreeBSD 5.4-RELEASE-p7 with the -L option. dump says: "Dumping snapshot of /dev/mirror/gm1s1h (/home) to ..." However when I later "restore -r" the filesystem, I keep getting messages like ./www/data/ASN/bay_3.log: (inode 805993) not found on tape e