[OpenAFS] solaris 10 versions supporting inode fileservers
Fri, 8 May 2009 10:33:20 -0400
Perhaps someone could update the inode fileserver to check whether the
filesystem is mounted with logging? And refuse to start if so?
It looks like a quick call to getmntany() would tell you.
It wouldn't prevent someone from coming along and remounting the filesystem
with logging enabled once the fileserver had started, but i imagine it will
save someone some trouble somewhere along the line.
On Tue, May 05, 2009 at 06:30:31PM -0400, Jason Edgecombe wrote:
> Harald Barth wrote:
> >>Does anyone have any information on which versions of solaris 10
> >>are not safe? Any direction to a bug report or a mail list thread
> >>would be appreciated.
> >I think the sneaky thing was that
> > a) UFS with logging may rot your files
> > b) Some update made logging the default mount option
> >I don't think ZFS is safe either.
> ufs without logging is the only safe option for the inode fileserver on
> The default logging option was changed in Solaris 9 9/04
> See http://docs.sun.com/app/docs/doc/817-5770/6ml72d6kd?a=view
> It's sneaky because the default is logging is on for disks over 100G or
> some similar threshold.
> UFS with logging WILL eat data with the inode server, you will have to
> salvage on each service restart when the /vicepX is unmounted and
> remounted (i.e. every boot/reboot).
> The namei fileserver is safe for ufs (with or without logging) and ZFS
> filesystems on solaris.
> Use namei, it's safer and faster on ufs w/logging than inode without
> BTW, where should I document tidbits like this?
> OpenAFS-info mailing list
Dan Pritts, Sr. Systems Engineer
office: +1-734-352-4953 | mobile: +1-734-834-7224
ESCC/Internet2 Joint Techs
July 19-23, 2009 - Indianapolis, Indiana