Package: e2fsprogs
Version: 1.41.0-3
Severity: grave
File: /sbin/fsck.ext3
Justification: renders package unusable

I am unable to get e2fsck to actually check my filesystem:

# fsck.ext3 /dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0
e2fsck 1.41.0 (10-Jul-2008)
fsck.ext3: Filesystem revision too high while trying to open 
/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)


The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Ok, let's try again:

# fsck -b 32768 /dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0 
fsck 1.41.0 (10-Jul-2008)
e2fsck 1.41.0 (10-Jul-2008)
fsck.ext2: Device or resource busy while trying to open 
/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0
Filesystem mounted or opened exclusively by another program?

As far as I can tell, nothing has the device open.

strace reveals something rather odd:

stat64("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
{st_mode=S_IFBLK|0660, st_rdev=makedev(253, 2), ...}) = 0
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDONLY|O_EXCL) = 4
close(4)                                = 0
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = 4
uname({sys="Linux", node="xerces", ...}) = 0
lseek(4, 33554432, SEEK_SET)            = 33554432
read(4, "\355A\0\0\0\20\0\0\26I~H,\6XH\16\272.H\0\0\0\0\0\0\3\0\10\0\0\0\0"..., 
1024) = 1024
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource busy)
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource busy)
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource busy)
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource busy)
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource busy)
open("/dev/mapper/luks_crypto_414ac43a-decb-4d06-81f6-10e9763c9cc0", 
O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource busy)

That is: fsck tries to open the device twice with O_EXCL, then complains
that it can't do so the second time!

Please lower the severity of this bug if you can't reproduce it.
Fortunately, I don't have any other broken filesystems around to test
this on.  :)

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages e2fsprogs depends on:
ii  e2fslibs                      1.41.0-3   ext2 filesystem libraries
ii  libblkid1                     1.41.0-3   block device id library
ii  libc6                         2.7-13     GNU C Library: Shared libraries
ii  libcomerr2                    1.41.0-3   common error description library
ii  libss2                        1.41.0-3   command-line interface parsing lib
ii  libuuid1                      1.41.0-3   universally unique id library

e2fsprogs recommends no packages.

Versions of packages e2fsprogs suggests:
pn  e2fsck-static     <none>                 (no description available)
pn  gpart             <none>                 (no description available)
ii  parted            1.8.8.git.2008.03.24-9 The GNU Parted disk partition resi

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to