I have a RAID-5 array on /home via vinum. This morning, the
server (running 4.8-PRERELEASE, compiled last week) wouldn't allow anyone
to login via ssh, imap, or console. So I had someone reboot the server
via control-alt-delete. Then it said that not all processes would dia,
use ps axl.
On Mon, 24 Feb 2003, Jaime wrote:
> As I type, the server is in single user mode. The fsck commands
> result in:
> CAN NOT READ: BLK 16
>
vinum is not started.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
New info for this problem:
S array.p0.s0
crashed
S array.p0.s1
up
S array.p0.s2
up
S array.p0.s3
stale
Should I just "vinum start" at the shell?
TIA,
Jaime
To Unsubscribe: send ma
Jaime wrote:
New info for this problem:
S array.p0.s0
crashed
S array.p0.s1
up
S array.p0.s2
up
S array.p0.s3
stale
Should I just "vinum start" at the shell?
Well, at this point you've got vinum started now.
I would fix the raid problem before bothering with an fsck, if
it were me.
--
Bill Mora
Hello,
I have one box with several gmirror filesystems. When the box panics I always
have to reconnect lost inodes and also inconsistent filesystems.
I never had this problem with non gmirrored mountpoints.
Also, the mirrored mountpoints are almost completely idel regarding writes.
Here's an err
