[OpenAFS] 1.4.5 namei on solaris 9 sparc requires AlwaysAttach for vice partitions
Derrick Brashear
shadow@gmail.com
Thu, 29 Nov 2007 15:45:51 -0500
------=_Part_9131_19457510.1196369151513
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Nov 29, 2007 3:34 PM, Jason Edgecombe <jason@rampaginggeek.com> wrote:
> Hi all,
>
> In my sordid saga to get a Sun fibre channel array working well with
> AFS, I found the following:
>
> When I upgraded the server to 1.4.5 namei, the fileserver would not
> mount the /vicep? partitions without doing a "touch
> /vicep?/AlwaysAttach" first. These are dedicated partitions on separate
> hard drives.
>
> I'm using a source-compiled openafs on solaris 9 sparc. openafs was
> compiled with the following options:
> CC=/opt/SUNWspro/bin/cc YACC="yacc -vd" ./configure \
> --enable-transarc-paths \
> --enable-largefile-fileserver \
> --enable-supergroups \
> --enable-namei-fileserver \
> --with-krb5-conf=/usr/local/krb5/bin/krb5-config
>
> We're using MIT kerberos 1.4.1 on the clients & fileservers with a 1.6.xKDC
>
> # mount | grep vicep
> /vicepa on /dev/dsk/c0t0d0s6
> read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d80006
> on Thu Nov 29 13:03:15 2007
> /vicepd on /dev/dsk/c0t3d0s6
> read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d80016
> on Thu Nov 29 13:03:15 2007
> /vicepc on /dev/dsk/c0t2d0s6
> read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d8001e
> on Thu Nov 29 13:03:15 2007
> /vicepb on /dev/dsk/c0t1d0s6
> read/write/setuid/intr/largefiles/xattr/onerror=panic/dev=1d8000e on Thu
> Nov 29 13:03:15 2007
>
> # grep vicep /etc/vfstab
> /dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /vicepa ufs 3
> yes -
> /dev/dsk/c0t1d0s6 /dev/rdsk/c0t1d0s6 /vicepb ufs 3
> yes -
> /dev/dsk/c0t2d0s6 /dev/rdsk/c0t2d0s6 /vicepc ufs 3
> yes -
>
> #cat SalvageLog
> @(#) OpenAFS 1.4.5 built 2007-11-28
> 11/29/2007 09:52:59 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager)
> 11/29/2007 09:52:59 No file system partitions named /vicep* found; not
> salvaged
>
> Does anyone know why this would be happening?
>
Probably a bug in the "what's acceptable as a vice partition" logic... which
I thought i fixed before 1.4.5; i bet i committed the wrong thing (because i
tested it)
------=_Part_9131_19457510.1196369151513
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div class="gmail_quote">On Nov 29, 2007 3:34 PM, Jason Edgecombe <<a href="mailto:jason@rampaginggeek.com">jason@rampaginggeek.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>In my sordid saga to get a Sun fibre channel array working well with<br>AFS, I found the following:<br><br>When I upgraded the server to 1.4.5 namei, the fileserver would not<br>mount the /vicep? partitions without doing a "touch
<br>/vicep?/AlwaysAttach" first. These are dedicated partitions on separate<br>hard drives.<br><br>I'm using a source-compiled openafs on solaris 9 sparc. openafs was<br>compiled with the following options:<br>CC=/opt/SUNWspro/bin/cc YACC="yacc -vd" ./configure \
<br> --enable-transarc-paths \<br> --enable-largefile-fileserver \<br> --enable-supergroups \<br> --enable-namei-fileserver \<br> --with-krb5-conf=/usr/local/krb5/bin/krb5-config<br><br>We're using MIT kerberos 1.4.1
on the clients & fileservers with a 1.6.x KDC<br><br># mount | grep vicep<br>/vicepa on /dev/dsk/c0t0d0s6<br>read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d80006<br>on Thu Nov 29 13:03:15 2007<br>
/vicepd on /dev/dsk/c0t3d0s6<br>read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d80016<br>on Thu Nov 29 13:03:15 2007<br>/vicepc on /dev/dsk/c0t2d0s6<br>read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d8001e
<br>on Thu Nov 29 13:03:15 2007<br>/vicepb on /dev/dsk/c0t1d0s6<br>read/write/setuid/intr/largefiles/xattr/onerror=panic/dev=1d8000e on Thu<br>Nov 29 13:03:15 2007<br><br># grep vicep /etc/vfstab<br>/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /vicepa ufs 3
<br>yes -<br>/dev/dsk/c0t1d0s6 /dev/rdsk/c0t1d0s6 /vicepb ufs 3<br>yes -<br>/dev/dsk/c0t2d0s6 /dev/rdsk/c0t2d0s6 /vicepc ufs 3<br>yes -<br><br>#cat SalvageLog<br>@(#) OpenAFS 1.4.5
built 2007-11-28<br>11/29/2007 09:52:59 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager)<br>11/29/2007 09:52:59 No file system partitions named /vicep* found; not<br>salvaged<br><br>Does anyone know why this would be happening?
<br></blockquote><div>Probably a bug in the "what's acceptable as a vice partition" logic... which I thought i fixed before 1.4.5; i bet i committed the wrong thing (because i tested it)<br> <br></div></div>
<br>
------=_Part_9131_19457510.1196369151513--