Subject: RE: Disappearing files.....[long, new case/infos]
From: Matthew Wilson (mwilson@real.com)
Date: Thu Dec 07 2000 - 12:39:20 EST
> If I am reading the code correctly, the encoding works as follows:
>
> four bits are used for the major device number
> three bits are used for the minor device number
> one bit is used to indicate a file or not
> The remaining 24 bits are used for the inode (with the top byte of the
> 4 byte inode being shifted down 8 and xor'd with the lower 24 bits)
>
> So if your major device number is greater than 15, or your minor
> device number is greater than 7, or your inode values exceed
> 16,777,215 then you may run into problems. For us, it is the minor
> device number that is the issue. I suppose things could be re-encoded
> to be more amiable to larger numbers of devices, but it is just an
> arbitrary solution, IMO.
I've got 4 100+ GB RAID volumes to deal with. They are on a mulit-host
external controller, so they just look like /dev/hda1 -> /dev/hdd1. 24
bits is fine for inodes, as there are only 13,000,000 or so. The problem
is the same as yours, the minor device number. mine are 1,17,33 and
49. So here's a question, in my case, as all the major numbers are the
same (8), would itbe evil to hack this hash function to give the major
bits to the minor?
also, the the bit to determine if it's a file or not neccesary?
another question, what if netatalk stopped giving out DIDs? What if every
time the Mac asked for DID xxx, netatalk asked for the full path? Yes, a
performance hit, but I'll take a performance hit over lost data any day.
Matthew
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:45 EST