Am 21.04.2010 19:55, schrieb Brian Cuttler: > > Stefan, > > I don't have what you need, I do have something very specific > and fairly ugly. > > We have a large ZFS pool, we have unique mount points for each > user directory and for samba shares. Maintaining a disklist for > this system would be administratively difficult.
[...] I now found the time and brain to read through your scripts ... looks quite usable to me. As you mentioned it is not what I am looking for as it scratches a different itch ... Additional questions: * How do you handle removed zfs-filesystems? If user simpson_bart is removed and his zfs-fs as well, this would result in your scripts removing the relevant DLE as well (if you accept the change). Doesn't that mean that you can't access the backups via amrecover anymore? (ok, I could test that myself here) * You seem not to have to take care of the size of one single DLE created by your scripts? AFAI remember you use quite big libraries for backups, so I assume your zfs-fs can't get too big ... and I also assume you define zfs-quotae ... This might be some useful feature for your setup, something that reads in the used space of each zfs-DLE and triggers a warning if it's bigger than some defined value. > Needless to say the daily mail generated with changes to the > disklist is ignored by everyone but myself and I have to run > the get and accept scripts myself. What else should we expect? ;-) Thank you, Stefan
