The most likely cause is you are dumping a live filesystem. "dump" descends below the user view into the underlying data structures of the file system. However, it can't snapshot the whole thing at a single point in time. Very likely, you have two or more related data items in the filesystem data structure, which were consistent at each point in time. However, dump read one, both changed, then it read the other. Its resulting view is inconsistent, and it is warning you of this.
You won't be able to restore some portion of that filesystem from that tape. Maybe you care, maybe you don't. Maybe we're talking a bunch of temporary spool files, or maybe it is your company's GL database. What's on sda6? My first suggestion is look at tonight's dumps. No message? No worries. Or not to many worries. Are you spot-checking your backups? I run dress-rehersal restores of arbitrarily chosen filesystems, from time to time, just to ensure for my own sanity that the backups are working. I'd advise every member of this list to do the same. On Fri, Feb 01, 2002 at 08:27:10AM -0800, Tanniel Simonian wrote: > Hello, > > I've all of a sudden gotten this error on my backup. Reading the content > of the message I receive this output: > > /-- 138.23.89. sda6 lev 0 FAILED [/sbin/dump returned 3] > sendbackup: start [138.23.89.40:sda6 level 0] > sendbackup: info BACKUP=/sbin/dump > sendbackup: info RECOVER_CMD=/sbin/restore -f... - > sendbackup: info end > | DUMP: Date of this level 0 dump: Fri Feb 1 00:29:49 2002 > | DUMP: Dumping /dev/sda6 (/home) to standard output > | DUMP: Added inode 7 to exclude list (resize inode) > | DUMP: Label: none > | DUMP: mapping (Pass I) [regular files] > | DUMP: mapping (Pass II) [directories] > | DUMP: estimated 66251 tape blocks. > | DUMP: Volume 1 started with block 1 at: Fri Feb 1 00:29:50 2002 > | DUMP: dumping (Pass III) [directories] > ? /dev/sda6: EXT2 directory corrupted while converting directory #15074 > ? > ? DUMP: error reading command pipe: Connection reset by peer > ? DUMP: error reading command pipe: Connection reset by peer > sendbackup: error [/sbin/dump returned 3] > \-------- > > > I've been running kernel 2.4.17 on the backup server, and 2.2.19 on the > host. This just happend last night, and I've been able to backup for many > many months. > > Google was no help on this problem. > > Tanniel Simonian > > -- ----------------------------------------------------------------- Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549 URL http://www.linuxjournal.com/ -----------------------------------------------------------------
