Hi!
> > > * Fault handling
> > >
> > > The filesystem must respond cleanly to *all* out-of-memory failures
> > > and media EIO errors. The response to ENOMEM may be to spin
> > > waiting for memory, and EIO may take the filesystem offline, but in
> > > either case when control returns to user space the filesystem must
> > > be in a known state in which all resources used by that syscall are
> > > released and the filesystem can be unmounted.
>
> > >From my games with ext2-over-nbd, I know ext2 fails this test. Make
> > filesystem bigger than partition and watch the hell.
>
> Working correctly in response to operator stupidity is a different
> thing.
It was not exactly operator _stupidity_.
> If your data is toasted there's a limit to what can be recovered. But in
> this case, did you really end up with something non-unmountable? ext2
> should have complained like mad, but it shouldn't have crashed.
It resulted in panic() as far as I can remember. It was long time ago.
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:35 EST