SCIENTIFIC-LINUX-USERS Archives

July 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Todd And Margo Chester <[log in to unmask]>
Reply To:
Todd And Margo Chester <[log in to unmask]>
Date:
Thu, 19 Jul 2012 11:09:31 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
On 07/19/2012 10:34 AM, Lamar Owen wrote:
> On Wednesday, July 18, 2012 03:47:22 PM you wrote:
>> Hi All,
>>
>> Any of you working with 6.3 beta know is the bug where
>> you drop to fsck at boot and its gives no visual indication
>> is fixed?  (One of these days I am going to just flip the power
>> off thinking it is crashed and ...)
>
> It's not a bug, it's a filesystem-dependent tunable parameter associated with your filesystem.
>
> On my RHEL 6.3 system here, looking at one 'post-install-created' filesystem:
> [root@www ~]# tune2fs -l /dev/sdh1|grep ount|tail -2
> Mount count:              11
> Maximum mount count:      31
> [root@www ~]#
>
> The /boot and / filesystems have a max mount count of -1, meaning to not do the check.  There's also the parameter:
> [root@www ~]# tune2fs -l /dev/sdh1|grep eck
> Last checked:             Sat Mar 17 11:29:41 2012
> Check interval:           15552000 (6 months)
> Next check after:         Thu Sep 13 11:29:41 2012
> [root@www ~]#
>
> This is pretty well documented in the tune2fs man page.
>
> It is a bit disconcerting to watch that bar at the bottom seemingly stop; edit your kernel command line options in /boot/grub/grub.conf (or menu.lst) to remove rhgb and quiet and you'll see the fsck start up.  You can interrupt the fsck with CTRL-C if desired.  As the filesystem I mentioned above is ~6TB in size and contains millions of files, it can take quite a long time to fsck.  Depending upon whether I'm in a maintenance window (with a standby online) or not will usually determine whether I let the fsck run or not, and I always try to allow enough time in scheduled maintenance windows for all attached filesystems to run fsck during the window (that is, I try to make the window long enough so that I don't have to rush the closing of the window).
>



Hi Lamar,

    Okay, not a bug, but really foolish, bearing in mind to
temptation to throw the power switch.  Especially when
an end user is in charge of the server (small business).

    What exactly does removing "rhgb" and "quiet" from my kernel
command line do?

Thank you for the help!
-T

ATOM RSS1 RSS2