On 08/06/2013 23:37, Tanstaafl wrote:
Hi everyone,
What is best practice for doing this?
If I reboot in single user mode, will my lvm volumes (ie, /var) be
available for fsck'ing, or do I have to mount them first?
The current problem started after a different problem required me to do
On 2013-06-09 3:45 AM, Alan McKinnon alan.mckin...@gmail.com wrote:
I'm not convinced a power outage broke the fs so that you now can't
umount it, I'm having a hard time imaging how that would happen. More
likely some other script file elsewhere is damaged and leaves files open
when the system
On 09/06/2013 16:43, Tanstaafl wrote:
On 2013-06-09 3:45 AM, Alan McKinnon alan.mckin...@gmail.com wrote:
I'm not convinced a power outage broke the fs so that you now can't
umount it, I'm having a hard time imaging how that would happen. More
likely some other script file elsewhere is damaged
On Sun, 09 Jun 2013 17:14:57 +0200, Alan McKinnon wrote:
I have a similar thing with my notebook and NFS mounts at home, I often
forget to umount the NFS dirs, causing issues when I then go to work and
wake the machine up
That's why I have my hibernate script unmount NFS shares and take the
On 2013-06-09 11:14 AM, Alan McKinnon alan.mckin...@gmail.com wrote:
On 09/06/2013 16:43, Tanstaafl wrote:
I do know the last few times this has happened, the NFS mount was
'unavailable' (the device had powered down without first unmounting it
from the server)...
I hope that is all it is...
Hi everyone,
What is best practice for doing this?
If I reboot in single user mode, will my lvm volumes (ie, /var) be
available for fsck'ing, or do I have to mount them first?
The current problem started after a different problem required me to do
a hard reset on the server - had to do with
6 matches
Mail list logo
