Bug#490984: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery required on readonly filesystem
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.
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 use debian installer standard installs.
I'd agree if I were installing a new system.
However, this is an existing system whose various
packages have been upgraded over time with
"apt-get install <package-name>"
What do you think?
Thanks,
Kingsley
On 07/16/08 10:47, maximilian attems wrote:
> On Tue, 15 Jul 2008, Kingsley G. Morse Jr. wrote:
>
> > Thanks for maintaining debian's kernel packages.
>
> hmm how is the bug you reported related to the kernel?
>
>
> please ask such support the next time on the debian user
> mailing list.
>
> > 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
>
> not reproducible here,
> please use debian installer standard installs.
>
> --
> maks
Reply to: