>>>>> "Phil" == W Phillip Moore <[EMAIL PROTECTED]> writes:
Phil> On a side note, I a, spending part of this week trying to add
Phil> support for >2GB filesystems on SunOS 4.1.3 into AFS 3.4.
Phil> Transarc supports filesystems "as large as the underlying OS",
Phil> but in the SunOS 4.1.3 case, that limit is still 2GB. If you
Phil> are using ODS, large filesystems are possible, but code changes
Phil> are also necessary.
Phil> I'm curious if anyone else has worked on this problem??
Phil> Transarc was suprised when I reported the lak of support as a
Phil> bug. The deeper I get into the code, I can see why it wasn't
Phil> "free".
Phil> If/when the code works, I beleive Morgan Stanley will be able to
Phil> make the patch to the 3.4 source tree available in the contrib
Phil> area, if there is significant interest.
I beleive I have this working, but before I put the effort into
getting public release of a source code patch approved, I'd like to
get some idea of the interest out there.
The code changes are not huge, in fact, only the salvager sources
needed to be modified. The fileserver and volserver I merely relinked
with libserver, which is a the ODS library which overloads a number of
libc functions. For example: fstatfs() and statfs(). This is
apparently enough to get the volserver to tell you that you have large
partitions.
The salvager needed to be coded to use lseek2, a version of lseek
which can take a 64-bit offset value.
The missing peice would be vfsck, which I haven't touched since we
took a different approach and merged the AFS functionality into the
ODS fsck sources (won't do you any good unless you are a Sun source
licensee).
I suspect that the changes are analagous to the salvager: use
lseek2(), not lseek().
Interested in the code?? Let me know. We are going to try to convince
Transarc to integrate and support it.
Phil
