- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Redhat fsck
Operating System - Linux
1752866
Members
3662
Online
108791
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 01:48 PM
тАО03-03-2011 01:48 PM
Redhat fsck
Hi,
We have a RH virtual machine that we had to reboot. It has approx 5.5tb of staorage attached via an IOMEGA NAS drive.
As the system hadn't rebooted in over 190 days, it's running and fsck - and taking forever, 5 hours so far, and we estimate we're about 25% complete.
Is there any safe way to reboot and bypass the fsck. I'm assuming we would need to get to something like "single user mode" and edit the fstab file.
Has anyone any ideas on how best to proceed?
Many thanks,
Paul
We have a RH virtual machine that we had to reboot. It has approx 5.5tb of staorage attached via an IOMEGA NAS drive.
As the system hadn't rebooted in over 190 days, it's running and fsck - and taking forever, 5 hours so far, and we estimate we're about 25% complete.
Is there any safe way to reboot and bypass the fsck. I'm assuming we would need to get to something like "single user mode" and edit the fstab file.
Has anyone any ideas on how best to proceed?
Many thanks,
Paul
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 04:08 PM
тАО03-03-2011 04:08 PM
Re: Redhat fsck
last field in /etc/fstab is for fsck, if I'm correct. Setting "0" there means no fsck needed during boot time. Usually no need to get to single user unless it is some system mount (i.e. /usr , /var etc). "fuser" will show you who uses the mountpoint.
So computers don't think yet. At least not chess computers. - Seymour Cray
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2011 04:20 AM
тАО03-05-2011 04:20 AM
Re: Redhat fsck
You did not specify the filesystem type, but I assume you're using ext3 filesystems, as it's the RedHat default...
To disable automatic filesystem checks based on number of mounts and time since last full check, you can use this command:
tune2fs -c 0 -i 0 /dev/
With this modification, the system will still run the journal recovery process at every boot-time fsck (which should be fast) and if a filesystem error was detected when the filesystem was used the last time, a full fsck will be performed (which will be exactly as slow as what you're now experiencing).
Is this the root filesystem or a separate data filesystem? If it's the root filesystem, editing /etc/fstab may have no effect, since the root filesystem is treated specially. The tune2fs command I specified above should still be effective.
Interrupting the fsck on a VM may be tricky. Too bad you did not specify your virtualization method - VMware, RedHat Xen, or something else?
Essentially, if you have a method to send the equivalent of a Ctrl-Alt-Del keypress to the VM, that should be a reasonably safe way to interrupt the boot process.
If this is the root filesystem, the standard boot to single user mode (using the kernel boot option "single") may be too late, as the boot process may check & mount the root filesystem before it presents the single-user mode command prompt. In that case, the boot option "init=/bin/bash" should work: it interrupts the boot process a bit earlier, leaving the root filesystem in read-only mode and all the other filesystems completely unmounted.
If you use "init=/bin/bash", your first steps should be:
mount /proc
mount -o remount,rw /
After that, remember that you will be in an extreme bare-bones environment: even the PATH variable may not include all the things you've come to expect by default.
MK
To disable automatic filesystem checks based on number of mounts and time since last full check, you can use this command:
tune2fs -c 0 -i 0 /dev/
With this modification, the system will still run the journal recovery process at every boot-time fsck (which should be fast) and if a filesystem error was detected when the filesystem was used the last time, a full fsck will be performed (which will be exactly as slow as what you're now experiencing).
Is this the root filesystem or a separate data filesystem? If it's the root filesystem, editing /etc/fstab may have no effect, since the root filesystem is treated specially. The tune2fs command I specified above should still be effective.
Interrupting the fsck on a VM may be tricky. Too bad you did not specify your virtualization method - VMware, RedHat Xen, or something else?
Essentially, if you have a method to send the equivalent of a Ctrl-Alt-Del keypress to the VM, that should be a reasonably safe way to interrupt the boot process.
If this is the root filesystem, the standard boot to single user mode (using the kernel boot option "single") may be too late, as the boot process may check & mount the root filesystem before it presents the single-user mode command prompt. In that case, the boot option "init=/bin/bash" should work: it interrupts the boot process a bit earlier, leaving the root filesystem in read-only mode and all the other filesystems completely unmounted.
If you use "init=/bin/bash", your first steps should be:
mount /proc
mount -o remount,rw /
After that, remember that you will be in an extreme bare-bones environment: even the PATH variable may not include all the things you've come to expect by default.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP