| 1 |
On 09/06/2013 16:43, Tanstaafl wrote: |
| 2 |
> On 2013-06-09 3:45 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
>> I'm not convinced a power outage broke the fs so that you now can't |
| 4 |
>> umount it, I'm having a hard time imaging how that would happen. More |
| 5 |
>> likely some other script file elsewhere is damaged and leaves files open |
| 6 |
>> when the system wants to umount /var. |
| 7 |
> |
| 8 |
> Hmmm.... |
| 9 |
> |
| 10 |
> Admittedly, I don't reboot this system often, so maybe I'm |
| 11 |
> misremembering when the problem crept in. |
| 12 |
> |
| 13 |
> Could it be the NFS mount that it is hanging on, and unmounting/var is |
| 14 |
> just that last thing showing on the screen? |
| 15 |
> |
| 16 |
> I think I'll try manually unmounting that before rebooting the next time |
| 17 |
> I need to(need to update the kernel soon anyway)... |
| 18 |
> |
| 19 |
> I do know the last few times this has happened, the NFS mount was |
| 20 |
> 'unavailable' (the device had powered down without first unmounting it |
| 21 |
> from the server)... |
| 22 |
> |
| 23 |
> I hope that is all it is... |
| 24 |
|
| 25 |
|
| 26 |
Ugh, NFS complicates things :-) |
| 27 |
|
| 28 |
I have a similar thing with my notebook and NFS mounts at home, I often |
| 29 |
forget to umount the NFS dirs, causing issues when I then go to work and |
| 30 |
wake the machine up |
| 31 |
|
| 32 |
If you have NFS in the mix, I'd certainly investigate that first before |
| 33 |
getting into more complex things. Also check that your NFS and mount |
| 34 |
stuff in /etc/init.d are doing the right thing in the right order with |
| 35 |
both startup and shutdown |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Alan McKinnon |
| 40 |
alan.mckinnon@×××××.com |
Archives