- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- file system bad blocks
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
10-09-2010 03:17 AM
10-09-2010 03:17 AM
In one of our storage (MSA 500), one of the disk fail, and we replace the disk. After replacing the disk for about a week, it resumes in rebuilding state. Then we reboot the storage along with the server and then it shows one of the lvol of vg01 is fail to up with the following error code:
dev/vg01/lvol3 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 8 has illegal block(s). Clear
Then we hash out the lvol and up the server, but when we try to mount the lvol it fails by showing some error as it has some bad blocks and need file system check. But file system check is not completing and goes hang after some time. Now, we running the below command:
fsck -yf dev/vg01/lvol3, and it progressing slowly without any error. My question is, what is the status of this, it is recovering or not? If its fail to recover, is there any other way to retrieve all data of the lvol as its very important to save those data.
Please response ASAP.
Rgds-Kranti
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2010 02:01 PM
10-09-2010 02:01 PM
SolutionThat is impossible to know for sure without a lot of diagnostics. If you have a support agreement, now is the time to use it.
The slow progress could mean that the disks have difficulties reading the data, but still manage to read it successfully after many retries.
Your MSA probably has at least one disk that is almost failing, perhaps more than one. If the filesystem check completes, you should immediately take a full backup of the data before using the MSA any further.
If the filesystem check fails, try to mount the filesystem in read-only mode, then backup as much data as you can. Then contact HP support for more advice, if possible.
A RAID is no substitute for regular backups. I fear you might be about to learn this the hard way. :-(
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2010 08:38 PM
10-09-2010 08:38 PM
Re: file system bad blocks
Tons of thanks for your valuable suggestions. Please tell me how to mount in read-only-mode only or any other way to retrieve data as we have to do so.
Secondly, is it feasible to login the storage through console to check the status right now or we should wait a little more as file system check it still progressing?
FYI, at present there are 2 disks that has problem, one failed yesterday morning, I reseat the disk and till now its in GREEN state. Another disk fail a month ago, I did replace that disk with a new one, but till now its in rebuilding state.
Please suggest to proceed.
Rgds-Kranti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2010 08:39 PM
10-09-2010 08:39 PM
Re: file system bad blocks
Sorry for my inadvertent spelling mistake of your name.
Rgds-Kranti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2010 12:27 AM
10-10-2010 12:27 AM
Re: file system bad blocks
from "man 1m mount":
-r Mount the specified file system as read-only.
Physically write-protected file systems must be
mounted in this way or errors occur when access
times are updated, whether or not any explicit
write is attempted.
so your command will be the
# mount -r /dev/vg01/lvol3 /mnt
Unix operates with beer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2010 12:31 AM
10-10-2010 12:31 AM
Re: file system bad blocks
# mount -o ro /dev/vg01/lvol3 /mnt
From the vg name, I thought it's about HP-UX. Maybe you're in a wrong forum?
Unix operates with beer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2010 02:16 AM
10-10-2010 02:16 AM
Re: file system bad blocks
The OS version is RHEL-4. Anyways, thanks for your suggestions...let me work on that and will get back to you ASAP.
Rgds-Kranti