On Mon, Oct 30, 2017 at 07:11:16PM +0100, Gionatan Danti wrote: > > that in theory are only reading and reporting information. I've also > > suggested that whenever repairs are done, lvm should record a persistent > > message in the system log with the details, but that idea didn't get a > > great reception. > > Just to know: why the idea of syslog reporting was discarded?
It was so obviously correct to me that I had a hard time arguing for it. I don't think any of the objections were satisfactory, e.g. nobody has asked, nobody needs it, the metadata archives are good enough, you can already configure log messages to go to syslog. I am still hoping to do something like this either as a part of centralizing metadata repair (in progress), or as a part of a broader suggestion that did get a better response but will take more work. That was to create a new log file and format in which every lvm disk change is recorded. https://bugzilla.redhat.com/show_bug.cgi?id=1455671 Everyone is encouraged to give their feedback about that in that bz, or create an "issue" on the lvm github. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
