Hi all, The box is a debian sarge, standard Debian kernel. Every morning I run dump on all filesystems, level 0 on Sundays, 1 on Mon and Thu, 2 on Tue and Fri, and 3 on Wed and Sat. I do this on live filesystems, mounted rw. All is well except occasionally (two times over the last four weeks - once on Friday and once on a Wednesday two weeks later) I get the following error when dumping the root partition:
[...] | DUMP: Dumping volume 1 on /srv/backup/2006-07-26_Wed_level_3/_001 | DUMP: Volume 1 started with block 1 at: Wed Jul 26 06:25:08 2006 | DUMP: dumping (Pass III) [directories] | /dev/mapper/lv-pv: Attempt to read block from filesystem resulted in short read while reading inode #2 | | DUMP: error reading command pipe: Connection reset by peer | DUMP: Broken pipe and dump exits with code 3 I could not find this message in dump source, so this is probably a libext2fs message, which all the more probable that most finds on Google are reports of running fsck on some seriously mangled filesystems. However my filesystem seems OK. I haven't run fsck on it yet, but the fact that the next dump (on the subsequent day) runs just fine, suggests that this is not an error in the filesystem. The strange thing is that inode #2 is the root directory itself, and stat reports: | File: `/' | Size: 1024 Blocks: 2 IO Block: 4096 directory | Device: fd01h/64769d Inode: 2 Links: 21 | Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) | Access: 2006-07-30 14:41:03.845422864 +0200 | Modify: 2006-07-13 09:12:30.663241896 +0200 | Change: 2006-07-13 09:12:30.663241896 +0200 Which means it wasn't modified nor changed (I never remember the difference) neither around the time dump ran, nor after that. Does anyone have a clue on what might be happening? Marcin -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
