From: Brian McCullough <bdmc@bdmcc-us.com> To: dm-devel@redhat.com, linux-lvm@redhat.com Subject: Re: [linux-lvm] storage-logger: Recording changes to the udev database Date: Thu, 26 Mar 2020 20:32:24 -0400 [thread overview] Message-ID: <20200327003224.GB3078@bdmcc-us.com> (raw) In-Reply-To: <20200326233144.GM17504@agk-dp.fab.redhat.com> On Thu, Mar 26, 2020 at 11:31:45PM +0000, Alasdair G Kergon wrote: > I'm experimenting with ways of recording changes to the udev database so > you can look back at the history of the storage stack on a particular > machine. This is still a work-in-progress, but it's reached a point > where I'd like more people to try it out. > > I've written a shell script that records data related to storage uevents > in the system journal and a perl script that helps you to interrogate > this data later to create a representation of the storage components. > > If you're interested, please try this out and let me know if you think > pursing this approach further would lead to something that you would > use and distributions should ship. Alasdair, I have downloaded and installed in a Debian 9 environment. There are a couple of differences that I have seen so far. First, most importantly, the udev rules are in /etc/udev/rules.d. Secondly, it appears that the journalctl command does not like the output fields option. I will install this on another machine that has a bit more device activity, and comment later. Brian > Alasdair > -- > agk@redhat.com > > _______________________________________________ > 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/ >
next prev parent reply other threads:[~2020-03-27 1:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-26 23:31 Alasdair G Kergon 2020-03-27 0:32 ` Brian McCullough [this message] 2020-03-27 19:50 ` Brian McCullough 2020-03-27 20:53 ` Alasdair G Kergon 2020-03-27 20:52 ` Brian McCullough
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200327003224.GB3078@bdmcc-us.com \ --to=bdmc@bdmcc-us.com \ --cc=dm-devel@redhat.com \ --cc=linux-lvm@redhat.com \ --subject='Re: [linux-lvm] storage-logger: Recording changes to the udev database' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).