I'm not sure what I did. The drive is an "internal" 2 TB drive that I use in a
drive dock, only for backups. It had not been checked in a long time and was
seriously hosed. That is why I ran fsck with -y: to get to a sane state where I
would not damage things further by doing file operations. I wound up with over
100 things in lost+found, almost all empty files and directories.
I have about 8 of these in various sizes. Very handy for off-site backups (keep
one in the house of a friend in the next town, rotate, repeat). The systems
they run on are on a reliable UPS, but that does not help much when Linux
crashes. Since these migrate, they are not automounted and not subject to
boot-time fsck scrutiny. I'll have to do something about that.
________________________________
From: Dave Gilbert <email address hidden>
To: <email address hidden>
Sent: Sat, October 1, 2011 3:57:43 PM
Subject: [Bug 864344] Re: fsck -y leaves problems behind
Well in the 1st run it does warn you that something odd happened:
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[23300069] is 2, inode.i_links_count is 1. They should be the
same!
Inode 23300069 ref count is 1, should be 1. Fix? yes
so I think after that warning all bets are off - and I can see from your df -h
that your /dev/sdg1 isn't mounted,
so it does look like an e2fsck bug it got to that point.
Can I ask what did you do to your fs to get it into this state where the fsck
started off with those
errors and can you describe the hardware.
Bug description:
Fixing an ext4 file system required multiple passes. This is
counter-intuitive in a program that will sometimes say something to
the effect that "problems remain" but did not do so this time.
I'm not sure what I did. The drive is an "internal" 2 TB drive that I use in a
drive dock, only for backups. It had not been checked in a long time and was
seriously hosed. That is why I ran fsck with -y: to get to a sane state where I
would not damage things further by doing file operations. I wound up with over
100 things in lost+found, almost all empty files and directories.
I have about 8 of these in various sizes. Very handy for off-site backups (keep
one in the house of a friend in the next town, rotate, repeat). The systems
they run on are on a reliable UPS, but that does not help much when Linux
crashes. Since these migrate, they are not automounted and not subject to
boot-time fsck scrutiny. I'll have to do something about that.
Kevin O'Gorman, Ph.D. mailto:<email address hidden> www.kosmanor. com/~kevin
Home Page: http://
_______ _______ _______ _______ ____
From: Dave Gilbert <email address hidden>
To: <email address hidden>
Sent: Sat, October 1, 2011 3:57:43 PM
Subject: [Bug 864344] Re: fsck -y leaves problems behind
Well in the 1st run it does warn you that something odd happened:
WARNING: PROGRAMMING BUG IN E2FSCK! info[23300069] is 2, inode.i_links_count is 1. They should be the
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_
same!
Inode 23300069 ref count is 1, should be 1. Fix? yes
so I think after that warning all bets are off - and I can see from your df -h
that your /dev/sdg1 isn't mounted,
so it does look like an e2fsck bug it got to that point.
Can I ask what did you do to your fs to get it into this state where the fsck
started off with those
errors and can you describe the hardware.
Dave
-- /bugs.launchpad .net/bugs/ 864344
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
fsck -y leaves problems behind
Status in “e2fsprogs” package in Ubuntu:
New
Bug description:
Fixing an ext4 file system required multiple passes. This is
counter-intuitive in a program that will sometimes say something to
the effect that "problems remain" but did not do so this time.
ProblemType: Bug gnature: Ubuntu 2.6.38- 11.50-generic- pae 2.6.38.8 11-generic- pae i686 edia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) en_US:en
DistroRelease: Ubuntu 11.04
Package: e2fsprogs 1.41.14-1ubuntu3
ProcVersionSi
Uname: Linux 2.6.38-
Architecture: i386
Date: Sat Oct 1 14:33:30 2011
InstallationM
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to: /bugs.launchpad .net/ubuntu/ +source/ e2fsprogs/ +bug/864344/ +subscriptions
https:/