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
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:
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: Dumping snapshot
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 example below. The file
[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. The file wins.dat was not dumped.
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 have never seen any data loss,
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-9 dumps
:(
I thought this should
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
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 tape or
expected next file 12345, got 23456
I thought this
[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 next file 12345, got 23456
I thought this should _never_ happen when dumping a snapshot.
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 tape or
expected next file 12345, got 23456
I thought this
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 on tape or
expected next file 12345, got 23456
I
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 the dump, I sometimes get messages like
foo.txt (inode 12345) not
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 causing the
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 or
expected next file 12345, got 23456
I thought this should _never_
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
I thought this should _never_ happen when dumping a snapshot.
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 this should _never_ happen when dumping a snapshot.
What is
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
expected next file 12345, got 23456
I'm seeing this too.
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
I'm seeing this too. It's always exactly one inode per file system.
You are
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 tape or
expected next file 12345, got 23456
I'm seeing this too. It's always
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
expected next file 12345, got 23456
I'm seeing this too. It's always exactly one inode per file
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.dmp
22 matches
Mail list logo
