Juri Haberland wrote:
>
> Florin Andrei wrote:
>
> > It's been a long time since i started to always do "sync; reboot"
> > instead of just "reboot". I've always felt this is safer.
> > But you're right, the OS should do that for me, at the right time.
> > Therefore, i've submitted a bug report to bugzilla.redhat.com:
> >
> > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=62025
> >
> > Please go to the bug report and add your own comments (actually,
> > everyone's invited to do that). I have a feeling that they will dismiss
> > it as "XFS specific" or something like that, which i believe would be
> > wrong.
> > But if quite a few people will agree with the solution proposed in the
> > bug report, maybe RH will fix the init scripts. ;-)
>
> Ahm, Florin, I think that the conclusion of this thread was that even
> multiple syncs don't help - instead you could just use 'sleep 30'.
>
> The bug must be somewhere in the kernel and it would be nice to know,
> whether it shows up with ext2/3 also or not. And also 2.4.18 just works
> with the same init script without the need of just a single 'sync' or
> 'sleep 30'...
>
> Juri
A script that uses fuser on files or directories that are known to have
problems could be quite useful. If they are not surviving with sync
called (still must probably wait a few seconds), and the kernel has a
problem, there is a good chance that it is because something is holding
those files open. Perhaps a script that does nothing more than write
syncronously to a special log file to name users of particular files or
directories would give some clues.
D. Stimits, stimits@xxxxxxxxxx
|