Wow, this is constructive. For the record, there is nothing wrong with my file system. There is, however, something wrong with the check that happens at boot. It is not user error, sorry if you think otherwise--doesn't change the facts. My suggestion is hardly (in the slightest) like telling people to drive around without seat belts. You ought to know just a little bit more about people before you simply start insulting them, Theodore. You know nothing about me--not one little thing.
On Sat, May 30, 2009 at 11:31 PM, andy baxter < a...@earthsong.free-online.co.uk> wrote: > Theodore Ts'o wrote: > > Hyperfitz, > > > > Can you open a new bug report, please? *Please* don't assume that > > just because you have the same symptoms as someone else, that it is the > > same bug. > > > > If two people went to the doctor, both complaining of a headache, one > > might just have the flu, and another might have brain cancer. It is > > not helpful to conflate the two in a single discussion. > > > Not sure how helpful this is, but isn't this really a problem with the > bug reporting system? Launchpad is used by (at least) 2 distinct groups > of people - ordinary users who are reporting a bug, and developers who > are trying to fix bugs. From the ordinary users point of view, they > don't know what the problem actually is yet - that's why they are > reporting a bug. So it makes sense from their perspective to organise > bugs by symptoms. > > From the developer's point of view, they are thinking more in terms of > what the underlying problem is, so it would make sense to organise bugs > in that way. (Which in the current system really means one bug report > per thread, unless someone has spent a fair amount of time investigating > the problem before submitting a report) > > Maybe what is needed is a more sophisticated bug tracker that > distinguishes between symptoms and underlying problem / cure, and lets > people view bug reports from either direction as it were. > > E.g. when you submit a bug, you would search for other people reporting > the same symptoms as you, and tag your report as having those symptoms. > Developers could then work through the set of bug reports tagged with a > given set of symptoms and decide which ones were likely to be caused by > the same underlying problem and tag them as related. Where the problem > is user error (such as a badly written fstab), the 'problem' tag could > direct them to a wiki page about how to fix the 'bug' at their end. This > would make the system more useful to users and also take some pressure > off developers. Where the problem is an actual bug, the tag would lead > to a thread about how the problem is being fixed. > > andy > > -- > 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 direct subscriber > of the bug. > > Status in “e2fsprogs” source package in Ubuntu: Incomplete > > Bug description: > Binary package hint: e2fsprogs > > Hello, > > I've just installed ubuntu dapper drake, and I have a persistent problem > where it fails the filesystem check during bootup, and I get dropped into a > root shell. Ignoring the problem lets me boot up, and if I check the > filesystem from the live CD (with fsck /dev/hda -f) it comes up clean. For > some reason it seems to be checking the root filesystem (/dev/hda5) even > though that's already been checked earlier on, and should be mounted at this > stage. The other filesystems check clean. I looked at the script > (/etc/rcS.d/S30checkfs.sh), and the fsck command includes the '-R' flag > which should tell it not to check the root filesystem, so I don't understand > why this is happening. As far as I can guess, the problem is that: a) for > some reason fsck is not picking up the fact that dev/hda5 is mounted as > root. b) because of this, it's checking the filesystem while still mounted, > and finding an error because of that. > > I've tried doing the following: > - booting from a live CD and checking the filesystem from that, including a > read/write bad blocks test. It always comes up clean or with a minor error, > but the same error comes up again when I reboot from the hard disk. > - rebuilding my partition table using fdisk (writing down the cylinder > numbers, deleting it and recerating it) > - looking at fstab. It's pasted below. > > # /etc/fstab: static file system information. > # > # <file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > /dev/hda5 / ext3 defaults,errors=remount-ro 0 > 1 > /dev/hda3 /local ext3 defaults 0 2 > /dev/hda1 /media/hda1 ext3 defaults 0 2 > /dev/hda4 /media/hda4 ext3 defaults 0 2 > /dev/hda7 /var ext3 defaults 0 2 > /dev/hda6 none swap sw 0 0 > /dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0 > /local/home /home auto defaults,bind 0 0 > /local/usr-local /usr/local auto defaults,bind 0 0 > > For the moment I'm carrying on using the system as it is, but I'm not happy > to do this in the long term if there's a persistent error. I've tried to do > everything I can to fix the problem, and it hasn't worked, so I'm filing > this as a possible bug. If you need any help finding the problem, I'm happy > to post logs etc. > -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
