Mark Post wrote:
On 8/6/2008 at 3:51 PM, in message <[EMAIL PROTECTED]>, Matt Gourley
<[EMAIL PROTECTED]> wrote:
-snip-
I've already tried running an fsck on the filesystem. Because I can't
write to it, I wound up shutting down and logging off the problem
system, LINKing its 201 disk MR to another running Linux system via
hcp(1), setting it online, and running fsck on it. No problems found.
Did you do an fsck, or an "fsck -f" command? What specific kernel level are
you at?
I ran an "fsck -f /dev/dasdb1", shutdown, came back up and all is well.
Thanks to Mark and Richard for giving me a couple more tools for the
toolbox.
-Matt
--
Matt Gourley
Systems Administrator
Pennsylvania State University
Administrative Information Services - Infrastructure/Sysarc
Rm 25 Shields Bldg., University Park, PA 16802
(814) 865-8726
[EMAIL PROTECTED]
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
