Re: [CentOS] Repair Filesystem prompt , after inode has illegal blocks

2009-09-14 Thread Ralph Angenendt 

On Sun, 2009-09-13 at 22:23 -0400, Robert Heller wrote:
 At Mon, 14 Sep 2009 11:23:19 +1200 CentOS mailing list centos@centos.org 
 wrote:
  A fault on our SAN dropped us down to a read-only filesystem 
 
 Just run fsck and follow the prompts.  Do this in single user mode.

That could be fun in a mode without network ... 

But yes, if the machine boots from there, fun will be had.

Ralph

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Repair Filesystem prompt , after inode has illegal blocks

2009-09-13 Thread Robert Heller 
At Mon, 14 Sep 2009 11:23:19 +1200 CentOS mailing list centos@centos.org 
wrote:

 
 Content-Language: en-US
 
 
 hi All,
 
 A fault on our SAN dropped us down to a read-only filesystem and after reboot,
 we have an Unexpected Inconsistency and I am being instructed by the boot 
 to run fsck manually
 without -a or -p  (this was after I think processing around 15% of the 
 filesystem)
 
 The specific message is  inode 27344909 has illegal blocks
 
 I recall running fsck some years ago on smaller and simpler systems - am 
 broadly
 familiar with what it is but have no expertise in using it to repair a 
 filesystem.
 
 Would be grateful for advice on whats the quickest / usual way to get us back 
 up from
 this. We do have a good backup for restoring unrecoverable files - i.e. I 
 assume I am going
 to end up  asking fsck to repair the filesystem itself and then clean up any 
 mess that
 results.
 
 This is fsck 1.39 , Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42
 
 thanks for any tips.

Just run fsck and follow the prompts.  Do this in single user mode. I
assume that this not a file system with the O/S itself on it (eg it is
not / or /usr or /var, etc.) If it ends up asking to do massive
repairs, it might be that the file system is totally fubar'ed, in which
case, doing a mkfs and doing a complete restore might be what you have
to do.  Be prepaired for this case. It is good that you have a good
backup!

 
 Cheers
 
 AMcC
 Bioinformatics Software Engineer
 AgResearch NZ
 
 
 
 
 
 
 ===
 Attention: The information contained in this message and/or attachments
 from AgResearch Limited is intended only for the persons or entities
 to which it is addressed and may contain confidential and/or privileged
 material. Any review, retransmission, dissemination or other use of, or
 taking of any action in reliance upon, this information by persons or
 entities other than the intended recipients is prohibited by AgResearch
 Limited. If you have received this message in error, please notify the
 sender immediately.
 ===
 MIME-Version: 1.0
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 
   
  

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Download the Model Railroad System
http://www.deepsoft.com/  -- Binaries for Linux and MS-Windows
hel...@deepsoft.com   -- http://www.deepsoft.com/ModelRailroadSystem/

 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Repair Filesystem prompt , after inode has illegal blocks

2009-09-13 Thread Les Mikesell 
Robert Heller wrote:
 At Mon, 14 Sep 2009 11:23:19 +1200 CentOS mailing list centos@centos.org 
 wrote:
 
 Content-Language: en-US


 hi All,

 A fault on our SAN dropped us down to a read-only filesystem and after 
 reboot,
 we have an Unexpected Inconsistency and I am being instructed by the boot 
 to run fsck manually
 without -a or -p  (this was after I think processing around 15% of the 
 filesystem)

 The specific message is  inode 27344909 has illegal blocks

 I recall running fsck some years ago on smaller and simpler systems - am 
 broadly
 familiar with what it is but have no expertise in using it to repair a 
 filesystem.

 Would be grateful for advice on whats the quickest / usual way to get us 
 back up from
 this. We do have a good backup for restoring unrecoverable files - i.e. I 
 assume I am going
 to end up  asking fsck to repair the filesystem itself and then clean up any 
 mess that
 results.

 This is fsck 1.39 , Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42

 thanks for any tips.
 
 Just run fsck and follow the prompts.  Do this in single user mode. I
 assume that this not a file system with the O/S itself on it (eg it is
 not / or /usr or /var, etc.) If it ends up asking to do massive
 repairs, it might be that the file system is totally fubar'ed, in which
 case, doing a mkfs and doing a complete restore might be what you have
 to do.  Be prepaired for this case. It is good that you have a good
 backup!

fsck -y will assume a 'yes' answer to all the prompts, which you might as well 
do unless you think you know more than fsck does about fixing the filesystem.

-- 
   Les Mikesell
lesmikes...@gmail.com


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos