On Fri, 11 Jan 2002 06:12, Andreas Dilger wrote:
>
> Well, given that the snapshot is now broken and LVM is refusing I/O on it,
> what do you expect the filesystem to do? This is what LVM _intends_ to
> happen, because the snapshot can no longer hold all of the data to keep
> it consistent.
>
> The ext3 error is reporting that it tried to read the directory (root = #2)
> and it got nothing back. The reason you see some files and not others is
> because those blocks happen to still be in the cache, and it does not go
> to LVM to try and re-read them. Eventually, as the memory is needed for
> other things, you will no longer be able to read anything.
>
> I suppose it would be possible to have LVM do an "unmount" of any fs
> using a bad snapshot device from within the kernel, but whether people
> actually want that to happen is another question entirely.
If this is what is considered normal operation then everything is fine.
Thats why I decided to ask - to find out :-).
>From my previous tests the behaviour I was observing was that once the
snapshot had overflowed a "ls" on the snapshot showed nothing. This still
appears to be the behaviour of resierfs.
Cool - if this is standard behaviour then everything seems fixed :-)
--
Adrian Head
(Public Key available on request.)
|