Subject: | |
From: | |
Reply To: | |
Date: | Sun, 28 Oct 2012 22:38:36 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 10/28/2012 09:13 PM, Chris Schanzle wrote:
> On 10/28/2012 03:29 AM, Todd And Margo Chester wrote:
>> On 10/27/2012 07:42 PM, Steven J. Yellin wrote:
>>> You can put an fsck command in /etc/rc.d/rc.local.
>>>
>>> Steven Yellin
>>>
>>> On Sat, 27 Oct 2012, Todd And Margo Chester wrote:
>>>
>>>> Hi All,
>>>>
>>>> SL 6.2, x64
>>>>
>>>> I have an "ext 4" drive (/dev/sdb1) I use for backup that is
>>>> deliberately not in my fstab.
>>>>
>>>> "touch /forcefsck" will only force a check on my main ("/")
>>>> drive.
>>>>
>>>> Question: is there a way to trigger an an fsck at boot on
>>>> this backup drive?
>>>>
>>>> Many thanks,
>>>> -T
>>>>
>>>
>>
>> Thank you. Thank will work.
>>
>> Actually, I am trying to solve the mystery of how to get it to
>> fsck at the same time as "touch /forcefsck". Do you know
>> how to do this?
>>
>> Many thanks,
>> -T
>
> Hi Todd,
>
> Have you perused through tune2fs(8) to notice you may set a
> max-mount-counts to 1 or maybe a daily interval-between-checks to 1d?
>
> Why are you so adverse to an fstab entry? If you specify option
> "noauto" it won't be mounted on boot, but it *might* fsck with the others.
Hi Chris,
Only certain scripts need access or even need to know this drive exists.
I deliberately do not have it in my fstab. I use this drive as you
would a removable flash drive.
What I am up to is trying to see if there is any clue as to why
I drop to maintenance mode every so often with a message that
fsck can not lock the drive because it is in use. Our intrepid
heroes at Red Hat are troubleshooting this for me:
https://bugzilla.redhat.com/show_bug.cgi?id=836696
"cat /proc/mounts" in maintenance mode does not even show the drive as
mounted (it is not suppose to be). And "lsof" shows nothing accessing
the drive (it is not mounted).
I am just digging around looking for any clue that might help them.
I just used your suggestion on "tune2fs -l /dev/mapper/lin-bak"
and posted it to the bug.
Thank you for the help,
-T
|
|
|