[linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Xen list at xenhideout.nl
Thu Apr 13 15:43:18 UTC 2017

Stuart Gathman schreef op 13-04-2017 17:29:

> IMO, the friendliest thing to do is to freeze the pool in read-only 
> mode
> just before running out of metadata.

It's not about metadata but about physical extents.

In the thin pool.

> While still involving application
> level data loss (the data it was just trying to write), and still
> crashing the system (the system may be up and pingable and maybe even
> sshable, but is "crashed" for normal purposes)

Then it's not crashed. Only some application that may make use of the 
data volume may be crashed, but not the entire system.

The point is that errors and some filesystem that has errors=remount-ro, 
is okay.

If a regular snapshot that is mounted fills up, the mount is dropped.

System continues operating, as normal.

> , it is simple to
> understand and recover.   A sysadmin could have a plain LV for the
> system volume, so that logs and stuff would still be kept, and admin
> logins work normally.  There is no panic, as the data is there 
> read-only.

Yeah a system panic in terms of some volume becoming read-only is 
perfectly acceptable.

However the kernel going entirely mayhem, is not.

More information about the linux-lvm mailing list