Looks like the mount points are all # (no%) and rooot.affs & root.cell have disappeared.
Will vos dump everything and remount all. The strangest thing is that some some machines the # mount points are writable; ted On Tue, Nov 15, 2011 at 8:40 AM, Marc Dionne <[email protected]>wrote: > On Sat, Nov 12, 2011 at 19:51, Ted Creedon <[email protected]> > wrote: > > I'm upgrading my Linux bpxes to open suse 12.1 RC2 (3.1.0-1.1) > > I wouldn't recommend running a 3.1 kernel with OpenAFS 1.6.0. There's > a bug that will eventually cause your system to hang under load. It > is fixed in the master branch, and will be part of any upcoming 1.6 > releases. > > > While openafs-1.6.0 compiles & installs OK the /afs/.creedon.biz file > system > > gets mounted RO > > > > Other 1.6.0 versions of the client on other boxes with older kernels > still > > are writable but the newer 1.6.0 client doesn't > > seem to work on kernel 3.1.0-1.1. but does work on kernel 2.6.34.7-0.7. > > > > > > eg: > > > > touch /afs/.creedon.biz/junk/foo > > touch: cannot touch `/afs/.creedon.biz/junk/foo': Read-only file system > > I have a few systems with 3.1 and 3.2-rc kernels (but running master, > not 1.6) and this behaves normally for my cells. > > Marc >
