On 09/13/2011 07:39 PM, Matt Garman wrote:
...
Also, as a side question: I always do this---let my servers run for a
very long time, power down to change/upgrade hardware, then forget
about the forced fsck, then pull my hair out waiting for it to finish
(because I can't figure out how to stop
On Tue, Sep 13, 2011 at 8:39 PM, Matt Garman matthew.gar...@gmail.comwrote:
My question is more along the lines of best
practices---what are most people doing with regards to regular fsck's
of ext2/3/4 filesystems? Do you just take the defaults, and let it
delay the boot process by however
On Tue, 2011-09-13 at 21:39 -0500, Matt Garman wrote:
I can't seem to find the answer to this question via web search... I
changed some hardware on a server, and upon powering it back on, got
the /dev/xxx has gone 40 days without being check, check forced
message. Now it's running fsck on a
On 09/13/11 7:48 PM, Always Learning wrote:
Would be nice if one could schedule this sort of work for off-peak.
the problem is, the file system has to be unmounted, so it pretty much
has to be offline.
--
john r pierceN 37, W 122
santa cruz ca
On 09/13/2011 09:39 PM, Matt Garman wrote:
I can't seem to find the answer to this question via web search... I
changed some hardware on a server, and upon powering it back on, got
the /dev/xxx has gone 40 days without being check, check forced
message. Now it's running fsck on a huge (2
On 09/13/11 8:57 PM, Tracy Bost wrote:
my first post here. that same thing happened with me a few years ago
with RHEL. i'm trying to remember the steps and seems like booted into
single user/rescue mode and then turned the fsck flag to off in fstab
for the partition(s). hope that can at least
6 matches
Mail list logo
