From: Pavel Machek <pavel@ucw.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [-mm] klibc breaks my initscripts
Date: Wed, 24 May 2006 00:36:52 +0200 [thread overview]
Message-ID: <20060523223652.GA1585@elf.ucw.cz> (raw)
In-Reply-To: <44738BA7.1020507@zytor.com>
Hi!
> >>[Adjusted Cc: list]
> >>
> >>Pavel Machek wrote:
> >>>>- a. What distro?
> >>>Hacked debian.
> >>>
> >>>>- b. What's the error?
> >>>Something about root not being mounted so it can't be remounted.
> >>I need the details on this one. This sounds like it could be the Debian
> >>mount getting confused by /proc/mounts and/or /etc/mtab.
> >
> >I cheated: I added "rw" to the command line. But results are the same
> >as in normal case, even strace looked the same.
> >
> >Any ideas?
> > Pavel
> >
>
> >read(3, "/dev/hda4\t/\text2\tdefaults,commit"..., 4096) = 601
> ^^^^^^
>
> Yes, check your /etc/fstab. You're trying (explicitly) to mount an ext3
> filesystem as ext2, but your /etc/fstab contains ext3-related options.
> This means that mount(8) will try to add them to the remount, and the
> remount will fail because you're passing options to the filesystem that the
> filesystem doesn't understand.
Aha, sorry for confusion. So it was not klibc merge but stricter
parser to mount commandline. Problems are now fixed, thanks.
(And swsusp works okay; now I could test it from multiuser mode).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-05-23 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 8:37 Pavel Machek
2006-05-23 17:36 ` H. Peter Anvin
2006-05-23 21:11 ` Pavel Machek
2006-05-23 21:18 ` H. Peter Anvin
2006-05-23 21:51 ` Pavel Machek
2006-05-23 22:24 ` H. Peter Anvin
2006-05-23 22:36 ` Pavel Machek [this message]
2006-05-23 22:41 ` H. Peter Anvin
2006-05-23 17:48 ` H. Peter Anvin
2006-05-23 18:19 ` Joshua Hudson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060523223652.GA1585@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®