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@xxxxxxxxxx> 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@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: Repair Filesystem prompt , after inode has illegal blocks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: Repair Filesystem prompt , after inode has illegal blocks
- From: Ralph Angenendt <ralph.angenendt@xxxxxxxxx>
- Date: Mon, 14 Sep 2009 11:20:28 +0200
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <200909140223.n8E2NmGS011398@xxxxxxxxxxxxxxxxxxx>
- References: <18DF7D20DFEC044098A1062202F5FFF32B62984EA9@xxxxxxxxxxxxxxxxxxxxxxxx> <200909140223.n8E2NmGS011398@xxxxxxxxxxxxxxxxxxx>
- References:
- Repair Filesystem prompt , after inode has illegal blocks
- From: McCulloch, Alan
- Re: Repair Filesystem prompt , after inode has illegal blocks
- From: Robert Heller
- Repair Filesystem prompt , after inode has illegal blocks
- Prev by Date: Re: Problems setting terminal size in termcap/xterm
- Next by Date: [Found] CentOS is dead, long live CentOS
- Previous by thread: Re: Repair Filesystem prompt , after inode has illegal blocks
- Next by thread: qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.
- Index(es):
 |