On Mon, Apr 09, 2007 at 12:05:01PM -0400, Gene Heskett wrote:
> Subtract the 00h, and you have the 254 its currently sitting at,
> apparently subject to the whims of an individual boot. If I build md as
> a module, then md will get 254 and device-mapper (dm_mod) will get 253,
> and if I build pktcdvd, the packet writing util for burning cd/dvd's, it
> will get one of those numbers, shoving device-mapper down to 252. This
> number does not change AFAIK, for any file/directory on that particular
> disk. To demo:
Is it the case, then, that any block device loaded as a module will get
a dynamically generated major device number? Or just devices which
don't have a fixed major yet?
> Device: fe00h/65024d Inode: 11534709 Links: 1
> And an inspection of the revelant files says its the decimal version,
> present as the first number of every line in the file AFTER line 1. So
> this is doable by a bash script I believe. But I'll need a nap and 3
> more cups before I start that project.
Could you send me a copy of your incremental file? AFAICT, they're
binary files, so I'm not sure how you're speaking of "lines"..
If there's private info in there, please use tar to make a new
incremental of a non-private directory, rather than munging the file.
Dustin
--
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/
|