Bug#367125: ext2_get_inode: bad inode number

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

"Peter Kruse" <pjodrr@gmail.com> writes:

> Hello Goswin,
>
>
> On 6/16/06, Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wrote:
>           I noticed this and can reproduce it by running exportfs -u,
>      umount,
>      resize2fs, mount, exportfs and then accessing some previously used
>      file on the nfs clients. The client (or server?) still has the old
>      inode numbers cached and directly access the inodes while the
>      resize2fs has removed it. The ext2-fs gives an error and remounts it
>      read-only.
>
>
> That's interesting, didn't think it was so easy to reproduce -
> have to try that.
> Does it  also remount  the filesystem read-only when mounted
> with the errors=continue mount option?

I would think not. I prefer to mount read-only on errors.

MfG
        Goswin