On Fri, Feb 27, 2015 at 5:09 AM, Jan Stary <h...@stare.cz> wrote: > This is current/amd64. > > After cleaning my machine I reconnected two of my disks in reverse; > what was sd0 is sd1 now, and vice versa. > > I do nightly dumps of the filesystems, > starting with level 0 on early Monday morning, > continuing with incremental 1, 2 etc through the week. > Usually this means that the Monday dump -0 is big, > and the subsequent incrementals are relatively small: ... > Now, on the night after I interchanged the disks, > the dump -4 of sd1a (/biblio) is huge again; apparently, > dump -4 is dumping everything again. > > Is this simply because /etc/dumpdates deals > with device names, as opposed to duids?
It sounds like you should start using the -U option on dump starting with your next level zero for each disk. I wonder if it could be made the default by first searching for an entry with DUID and lower dump level, and falling back to a device name entry if no matching DUID entry was found or if they were just for higher dump levels. Once you do a level zero for a DUID it'll never look for a device entry again, but during the transition I think that strategy would find the same device entries that it would otherwise have found. Philip Guenther
