Maks,
Thank you for telling me about the discussion of 2.6.26
at the kernelnewbies page.
I read it.
Since we don't KNOW what's causing the bug, it
involves data corruption, it's still happening,
and I'd like to try a few more diagnostic
techniques, I'd like to keep this bug open.
Feel free to share your thoughts on ways to
diagnose why a mount command would sometimes fail
in /etc/init.d/umountroot.
So far, I've found...
it started failing after installing 2.6.25, and
it happens less often if either a
"cat /proc/mounts" is done, or
ALSA is reconfigured.
Best regards,
Kingsley
On 07/17/08 07:39, Debian Bug Tracking System wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the linux-image-2.6-686 package:
>
> #490984: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery
> required on readonly filesystem
>
> It has been closed by maximilian attems <[EMAIL PROTECTED]>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact maximilian attems
> <[EMAIL PROTECTED]> by
> replying to this email.
>
>
> --
> 490984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490984
> Debian Bug Tracking System
> Contact [EMAIL PROTECTED] with problems
> Date: Thu, 17 Jul 2008 09:33:04 +0200
> From: maximilian attems <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Bug#490984: linux-image-2.6-686: / is busy causes EXT3-fs:
> INFO: recovery required on readonly filesystem
>
> On Wed, 16 Jul 2008, Kingsley G. Morse Jr. wrote:
>
> > Hi Maks,
> >
> > Thank you for replying quickly.
> >
> > On 07/16/08 10:47, maximilian attems wrote:
> > [...]
> > > hmm how is the bug you reported related to the kernel?
> > [...]
> >
> > To be fair, I'm not sure that the kernel is to
> > blame.
>
> closing as bug is unreproducible and certainly not a kernel bug.
>
> > It could be data corruption (I'm recovering from a
> > bad CPU chip), incompatible package versions, or
> > even something else I suppose.
> >
> > However, I suspect the kernel because the
> > changelog at kernel.org for the next version,
> > 2.6.26, mentions the words "mount" and "remount"
> > hundreds of times, which leads me to suspect bugs
> > and active development.
>
> please read the kernelnewbies page about 2.6.26
> it will tell you a lot about ro bind mounts.
> nothing to be worried about.
>
> best regards
>
> --
> maks
>
> From: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]>
> To: Debian Bug Tracking System <[EMAIL PROTECTED]>
> Subject: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery
> required on
> readonly filesystem
> X-Mailer: reportbug 3.31
> Date: Tue, 15 Jul 2008 12:14:05 -0700
>
> Package: linux-image-2.6-686
> Version: 2.6.25+14
> Severity: normal
>
>
> Thanks for maintaining debian's kernel packages.
>
> They're a remarkable technology in more ways than
> one.
>
> Here's how I duplicate the bug.
>
> 1.) $ shutdown -r now
>
> 2.) ctl-alt-F7
>
> 3.) look quickly for something like
>
> "mount: / is busy"
>
> 4.) After the system has rebooted, if the root
> filesystem is EXT3, look for
>
> EXT3-fs: INFO: recovery required on readonly filesystem.
>
> in /var/log/messages.
>
> If the root filesystem is EXT2, I get a long,
> slow fsck recovery.
>
>
> It seems to me that this can be partially
> explained by the shutdown command running a
> script named
>
> /etc/init.d/umountroot
>
> which calls the "mount" command to remount the
> root file system as read only.
>
> It fails, and complains that
>
> "/ is busy"
>
> Since the root file system wasn't cleanly
> unmounted, it'll be recovered during the next
> boot.
>
> I investigated other processes interfering with
> the root file system, without result.
>
> However, it seems that inserting
>
> "cat /proc/mounts"
>
> just before the (re)mount command in
>
> /etc/init.d/umountroot
>
> usually allows mount to complete.
>
> As an aside, the words "mount" and "remount" occur
> hundreds of times in the changelog for 2.6.26.
>
> Frankly, I'm a little worried about data
> corrutpion.
>
> Thanks,
> Kingsley
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers unstable
> APT policy: (990, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.25-2-686
> Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
>
> Versions of packages linux-image-2.6-686 depends on:
> ii linux-image-2.6.25-2-686 2.6.25-6 Linux 2.6.25 image on
> PPro/Celeron
>
> linux-image-2.6-686 recommends no packages.
>
> -- no debconf information
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
