@willdeans: thanks for the strace. It was very useful indeed. Can you
try e2fsprogs 1.42.6 and see if the problem still occurs with that
version? The fact that you are seeing the "fallback back to backup
descriptors", "nope, that didn't work", etc., twice was something that
was fixed in 1.42.2,
"In any case, this isn't an e2fsck bug. The kernel is returning EBUSY;"
<-- why couldn't the kernel be returning EBUSY because of an e2fsck bug
which attempts to open the device twice (without first closing it)?
Why do I see in the E2fsprogs 1.41.13 (December 13, 2010) release notes:
http://e2fsp
#
# possible bug encountered running EXT2FS 1.42
# open call on device with no corresponding close
#
deans@deans2188:~$ sudo e2fsck -V
e2fsck 1.42 (29-Nov-2011)
Using EXT2FS Library vers
@DavaQB nope, not listed there either (I now have the same problem
again). Not in /etc/mtab or /proc/mount. lsof does not return anything
either. I will now go to single user mode again and see there, but I
think this is a fedora bug. Any hint where else the kernel stores
information about mounted
Just another thought that helped me with another issue...run:
/sbin/dmsetup table
If disk is listed there, it will be marked busy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711799
Title:
e2fsp
Philipp, the reason why tune2fs showed that it was not clean is either
(a) because in fact the file system was mounted, or (b) the system had
previously crashed while the file system was mounted.
If in fact e2fsck later said that the file system was clean, then that's
actually a pretty good indica
I now tried in single user mode and there I could run the check. It even
said it was clean? (Looking at what tune2fs said, that is - for me -
surprising).
I did run lsof on the partition, but it did not return anything.
It might have been an unclean shutdown of gparted, leaving either parted or
n
Looking at the strace which Philipp provided, what is happening is that
an exclusive open of the device is returning EBUSY from the kernel:
open("/dev/sdb1", O_RDONLY|O_EXCL) = -1 EBUSY (Device or resource busy)
This means that either (a) the device is mounted, (b) some other program
has th
I think I got hit by this problem too.
Fedora 16
# e2fsck -V
e2fsck 1.41.14 (22-Dec-2010)
Benutze EXT2FS Library version 1.41.14, 22-Dec-2010
The device is definitely not mounted.
However I can mount and use the device as usual. Just once I umount it
(and it is not listed any more on /pr
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711799
Title:
e
The directory names are not enciphered, they are replaced by unique
filenames AAA, BAA, CAA, DAA, etc.
The relevant section of code is:
memset(cp, 'A', dirent->name_len);
len = dirent->name_len;
id = name_id[len]++;
while ((len > 0)
I did read the man page and noted the scramble option. In fact, I did
save a scrambled image before I recovered my partition but the man page
is vague on how the names are (one-way?) ciphered and the e2image.c code
had little comments to help explain it so I am not willing to publish my
image anywh
If you had read the e2image man page, you would have seen that it
doesn't send any data blocks; just the file system metadata. It does
send the directory and file names, but there is a scramble option that
scrambles the file names leaving only the directory topology.
I'll note that Ubuntu 11.04
Sorry, I am not keen to disclose my private data. I am OS atm with only
my failed ubuntu10.10 laptop and a 10.10 live cd. It seems this is a
problem in 10.10 only (i.e. kernel related?). I just went down to the
nearest bookshop, bought a UK linux user magazine which had a xubuntu
11.04 live cd. Boo
Can you send me a raw e2image dump of your /dev/sda2 file system?
Please see the man page of e2image, under "RAW IMAGE FILES", for more
details, but basically it's something like this:
e2image -r /dev/sda2 - | bzip2 > /tmp/sda2.e2i.bz2
This will allow me to reproduce the problem. I
I am suffering this bug on my 10.10 laptop. It just decided to not boot
anymore last night. According to TT, I downloaded the latest e2fsprogs
1.41.14 from sourceforge, built and installed it, but still get the
error:
% sudo fsck /dev/sda3
fsck 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
fs
I encountered the same problem and fixed it by booting with a 11.04
(Natty) LiveCD (e2fsprogs @ 1.41.14-1ubuntu3). This should really be
backported into the 10.04 LTS livecd if possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the slow response.
"What you are reporting is something else. Can you tell me what the
older version of e2fsck said that it fixed?"
Sorry?
What ver 1.41.3 on Slax 6.1.2 said while fixing the partition/FS?
I didn't see it for my own eyes, but had it read out to me and it was
the usual
So what has been specifically fixed is this case:
# fsck.ext4 /dev/sde1
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Group descriptors look bad... trying backup blocks...
fsck.ext4: Bad magic number in super-block when using the backup blocks
fsck.ext4: going back to original superblock
fsck.ext4: Devi
Thanks for the response Theodore.
Yes it was definitely not mounted. I checked /proc/mounts (grep sda1
/proc/mounts), the mount -l command itself and also issued several
umount /dev/sda1 to be sure. (I do have 10 years of Linux experience.)
The output from e2fsck /dev/sda1 was the same as others
It definitely is fixed in 1.41.13 and 1.41.14.If you are using a
systemrescuecd 2.1.0, are you sure it didn't try mounting the root file
system before you ran the e2fsck manually? Can you check /proc/mounts
to be absolutely sure it's not really mounted?
It's not that I don't trust you, but,
This seems to me as a bug from upstream that is filtering down through
the distro's.
Using Ubuntu 10.10 LiveCD's e2fsck from the e2fsprogs package 1,41,12
failed to check an ext4 disk with errors saying the aforementioned
error.
Using a systemrescuecd-x86-2.1.0 CD's e2fsck from the e2fsprogs pack
I have tried with e2fsprogs 1.41.14 and I am seeing the same result. So
I am not sure if this is a different issue I have here
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711799
Title:
e2fspro
I can confirm I have also been hit with this problem.
Ubuntu 10.10 using e2fsprogs 1.41.12
There doesn't seem a clear upgrade path to 1.41.14 due to unsatisfied
dependencies. If anyone knows otherwise I would be happy to hear.
--
You received this bug notification because you are a member of Ub
"if you're using e2fsprogs 1.41.12, you really should upgrade..."
Make that better to "if Ubuntu is using e2fsprogs 1.41.12, Ubuntu really
should upgrade...". And since it is a bug affecting all 10.10 (at
least), it needs to enter the official upgrade path, urgently. What I
used was the installer-
Sigh, I was typing too fast.
The first sentence of the 3rd paragraph above should read:
So this is a problem that won't occur for _all_ cases of file system
corruption, but for a user which does have both the original and backup
superblocks corrupted, the results are rather catastrophic...
--
Y
The fix for this is in e2fsprogs 1.41.13, but I strongly recommend you
fix this by going to e2fsprogs 1.41.14, which which has additional bug
fixes. From the RELEASE-NOTES file:
Fixed a bug in e2fsck where if both the original and backup superblock
are invalid in some way, e2fsck will fail going
I have some problem with your patch in #2. It 'helps' on the short run; but the
actual bug is elsewhere, and a tad more serious.
Look at my first post: Even if the fsck dies as both of us found out, the
'mount' starts (so it finds the partition to be not mounted, okay), but never
continues, nev
I can't change the Importance, though it looks like a 'major', since everyone
with a crash will lose their installs. 99% will not know any better than to do
a reinstall; and probably quite a number of users will already have done so by
now; destroying the positive user experience of netbook 10.1
This one-line patch - add ext2fs_close(fs) in unix.c - seems to fix it:
if ((orig_retval == 0) && retval != 0) {
com_err(ctx->program_name, retval,
"when using the backup blocks");
Same error, different circumstances:
# fsck.ext4 /dev/sde1
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Group descriptors look bad... trying backup blocks...
fsck.ext4: Bad magic number in super-block when using the backup blocks
fsck.ext4: going back to original superblock
fsck.ext4: Device or resourc
31 matches
Mail list logo
