1.2.9 unstable ? (was [OpenAFS] inaccessibble volume - please help)

[Derrick J Brashear]

On Thu, 22 May 2003, Rudolph T Maceyko wrote:

> > Perchance do you know if "umount /afs" succeeded or failed?
> > If it failed, afsd -shutdown would return EACCES and never trigger the
> > code path which I believe is suspect.

Ok, so I think we haven't tested anything, because if /afs fails to
unmount, afsd -shutdown is a no-op, and you never get to the point where
the suspected problem is.

> Normal shutdown:

1.2.9? with patch?

>   Stopping AFS services.....
>   WARM shutting down of: CB... afs... BkG... CTrunc... AFSDB...
> RxEvent... RxListener...
>   afs_cacheDp 1 at stop
>     .
>     .
>     .
>   Shutting down interface eth0:  [  OK  ]
>   Shutting down loopback interface:  [  OK  ]
>   Starting killall:  [  OK  ]
>   Sending all processes the TERM signal...
>   Sending all processes the KILL smd: recovery thread got woken up ...
>   ignal...
>   Syncing hardware clock to system time
>   Turning off swap:
>   Turning off quotas:
>   Unmounting file systems:
>   Please stand by while rebooting the system...
>   flushing ide devices: hdc
>   Restarting system.
>
> Rudy
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>