HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Having to e2fsck manually
Operating System - Linux
1828404
Members
3446
Online
109977
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
08-14-2002 04:58 PM
08-14-2002 04:58 PM
All,
I am sure on some occasion you have experience a hard-reboot. Sometimes a hard re-boot requires manual intervention with e2fsck. How does one properly do this w/o risking corrution when the file system you need to do this on is root and it's mounted? e.g: When I get this prompt "crontrol D to reboot or enter root's password for maintanence", I usually enterl root's password and clean the root filesystme with "/sbin/e2fsck -y -b 32768 /dev/hda2". Is this way to do it? or is there a better of doing this w/o risking file system corruption? Thanks.
I am sure on some occasion you have experience a hard-reboot. Sometimes a hard re-boot requires manual intervention with e2fsck. How does one properly do this w/o risking corrution when the file system you need to do this on is root and it's mounted? e.g: When I get this prompt "crontrol D to reboot or enter root's password for maintanence", I usually enterl root's password and clean the root filesystme with "/sbin/e2fsck -y -b 32768 /dev/hda2". Is this way to do it? or is there a better of doing this w/o risking file system corruption? Thanks.
Reputation of a thousand years can be determined by the conduct of an hour
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2002 05:53 AM
08-16-2002 05:53 AM
Solution
There is little risk of corrupting the file system
by running e2fsck. However it can delete or truncate files
where the file system information is incomplete.
I would drop the switches and
run 'e2fsck /dev/hda2'. This
will use the default superblock and prompt you
before any changes. Add the
-b 32768 switch if the
superblock can't be found.
The effects of e2fsck I have
encountered are:
- log files truncated in the middle of a record.
- files being created during shutdown removed.
- files without a directory entry removed.
by running e2fsck. However it can delete or truncate files
where the file system information is incomplete.
I would drop the switches and
run 'e2fsck /dev/hda2'. This
will use the default superblock and prompt you
before any changes. Add the
-b 32768 switch if the
superblock can't be found.
The effects of e2fsck I have
encountered are:
- log files truncated in the middle of a record.
- files being created during shutdown removed.
- files without a directory entry removed.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP