Hi!
> >Did this succeed? If the application is still
> >truncating that file, the
> >umount should have failed.
>
> Actually, what I expect to happen is for the remount,ro
> to block until the file deletion completes. But it
> doesn't.
>
> Once a f/s is read-only, there should be NO writing to
> it. Right?
Linux happily writes to filesystems mounted read-only. It will replay
journal on them.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
