On Sat, May 30, 2009 at 04:28:53PM -0000, Hyperfitz wrote:
>
> Sure, if I have this problem again I will do all of this stuff that you ask.
> But the name of the thread is "filesystem check fails on boot, but
> filesystem isn't bad." This is a problem that it seems that not only I have
> had. I think it is probably is helpful to tell people that they can delete
> the fsck binaries and it will solve the problem.
Um, that's a terrible solution. It can lead to serious data loss. If
you do that and you end up losing lots of data, *please* don't blame
me, or ext2/3/4, or e2fsprogs. That's the rough equivalent of
disabling the seat belts on a car. You may be fine for a while, but
sooner or later you may end up finding yourself getting flung head
first through the windshield, suffering perhaps catatrphic damage.
> With respect to user error,
> the 8.10 install was straight off the official release CD. The only thing
> that I did differently than the absolute basic install was to partition some
> free space on my hard drive for the new file system. If the "out-of-the-box"
> installer cannot configure fstab correctly based on that kind of an
> operation, then that is hardly user error.
I've used the Ubuntu 8.10 installer, and it handles a second
filesystem *just* *fine*. So I don't know what you did; it could be
user error, it could be a hardware error.
> There are dozen of "flus" that people catch that are not caused by
> influenza: point taken. The same medicine, however, usually helps you feel
> better with all of them.
But taking medicine for the flu when you really have brain cancer
won't help you. And the symptoms for heart burn, a pulled muscle in
the torso, and a mild heart attack can also be the same --- and trust
me when I tell you that if you assume you have one disease when you
have another, the consequences can be quite fatal. A lot of people
die all around the world because they don't recognize the symptoms of
a heart attack, and assume it's something else minor.
> Name of thread: "filesystem check fails on boot, but filesystem isn't
> bad."
>
> Problem I am having: filesystem check fails on boot, but filesystem isn't
> bad.
Yes, but *why* does the filesystem fail? With what error message?
Suppose you told a car mechanic, the problem was, "the car has fuel in
the tank, but it doesn't go"; it must be the same problem as someone
else who says, "the car has fuel in its tank, but it doesn't go" ---
it *must* be the same problem. Would you not expect the car mechanic
to not roll his eyes heavenward and ask himself why is he wasting his
time giving free advice on the internet?
Look, I designed the filesystem, and I'm telling you that (a) this is
working correctly for millions of users, and (b) there are many, MANY,
reasons why you people could be seeing failures with superficially
similar symptoms as the one syou have given. I'm offerring to help
you for free; Canonical doens't pay me to help out Ubuntu users.
There are many senior developers on the Linux Kernel Mailing list who
refuse to help out users on Ubuntu launchpad because the quality of
bug reporting is *so* *bad*. It's a frustrating waste of their time,
and they've decided they have better things to do with their time than
to subject themselves to this sort of abuse by clueless users.
Every time I get this kind of talk from a clueless Ubuntu user, it
gets me *that* *much* closer to deciding that I should just give up on
Launchpad, because there's no intelligent life here.
> I thought it might be useful to someone else who was having the same (or a
> similar) problem to know that deleting the fsck binaries fixes the problem
> for me.
That's like saying, gee, the car doesn't go because the emergency
parking brake cable is frozen shut --- we can fix the problem by
removing the right front and left rear brake pads. Yes, that solves
the problem, but the car is substantially more dangerous to drive.
> If the problem happens again I will do all the stuff that you ask before I
> post.
Thank you...
- Ted
--
filesystem check fails on boot, but filesystem isn't bad
https://bugs.launchpad.net/bugs/48563
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
