also sprach Roger Leigh <[EMAIL PROTECTED]> [2008.07.25.1241 +0200]: > This turned out to be a problem with fscking LVM snapshots of live > ext3 filesystems. They would occasionally fail to fsck due to being > in an inconsistent state (because the snapshot is of the block dev, > the filesystem metadata isn't necessarily synched on snapshot). With > other filesystems, e.g. block devices, we can't be sure they aren't > already mounted somewhere else, where fsck would be dangerous (though > fsck should pick that up).
It turns out that I can't use my chroots anymore and this might be related: Build started at 20080729-2057 ****************************************************************************** + [ -f /etc/schroot/script-defaults ] + . /etc/schroot/script-defaults + FSTAB=/etc/schroot/mount-defaults + COPYFILES=/etc/schroot/copyfiles-defaults + [ -x /usr/bin/sbuild ] + SBUILD=true + [ normal = verbose ] + [ lvm-snapshot = block-device ] + [ lvm-snapshot = lvm-snapshot ] + [ setup-start = setup-start ] + ret=0 + /sbin/fsck -a /dev/chroots/sid-amd64-ea06953d-9a19-4a47-b242-5cee56be00b1 + : + exit 0 E: fsck 1.40-WIP (14-Nov-2006) /dev/chroots/sid-amd64-ea06953d-9a19-4a47-b242-5cee56be00b1: clean, 17383/524288 files, 159534/1048576 blocks sid-amd64-ea06953d-9a19-4a47-b242-5cee56be00b1: Chroot not found Can't close schroot pipe getting chroot data at /usr/share/perl5/Sbuild/Chroot.pm line 81. If I exit 0 before the fsck, then it works. If the fsck gets to run, it doesn't. Might this be related? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
