Hi all,
I'm makara from Cambodia. I'm freebsd newbie. I try to configure vinum I always
get this messages every time when I start vinum
vinum: Inappropriate ioctl for device
and a few minute later my pc is restart. I hope you can solv the problem.
Thanks sorry for my english.
On Sun, 2005-03-27 at 16:59, Ean Kingston wrote:
On March 27, 2005 10:35 am, Robert Slade wrote:
Hi,
I have managed to setup a vinum volume using 2 striped disks, the
volume
is created and I can do newfs on it and mount it.
However, when I set start_vinum=YES in rc.conf, vinum
Hi,
I have managed to setup a vinum volume using 2 striped disks, the volume
is created and I can do newfs on it and mount it.
However, when I set start_vinum=YES in rc.conf, vinum loads then I get
panic, followed by hanging vnode.
I'm using 5.3.
Any pointers please.
Rob
On March 27, 2005 10:35 am, Robert Slade wrote:
Hi,
I have managed to setup a vinum volume using 2 striped disks, the volume
is created and I can do newfs on it and mount it.
However, when I set start_vinum=YES in rc.conf, vinum loads then I get
panic, followed by hanging vnode.
I'm using
On Sun, 2005-03-27 at 16:59, Ean Kingston wrote:
On March 27, 2005 10:35 am, Robert Slade wrote:
Hi,
I have managed to setup a vinum volume using 2 striped disks, the volume
is created and I can do newfs on it and mount it.
However, when I set start_vinum=YES in rc.conf, vinum loads
Hello,
I have a really weird problem, I don't know if it is software or
hardware related. When I am in the process of extracting a multivolume
archive (rar) it goes on for a while, then stops, then continues and
then all of the sudden the computer reboots.
The volume which I try to extract
On Wednesday, 2 June 2004 at 11:55:37 +0200, Erik Mossberg wrote:
Hello,
I have a really weird problem, I don't know if it is software or
hardware related. When I am in the process of extracting a multivolume
archive (rar) it goes on for a while, then stops, then continues and
then all of
On Thursday, 5 February 2004 at 6:48:18 +0100, Ole Voss wrote:
Last night I reinstalled freebsd and obviously somewhere along the way my
400GB concat vinum volume wasn't unmounted (at least that's what freebsd
told me). Now, when I run 'fsck -t ufs /dev/vinum/abyss'
I get this:
titan#
Last night I reinstalled freebsd and obviously somewhere along the way my
400GB concat vinum volume wasn't unmounted (at least that's what freebsd
told me). Now, when I run 'fsck -t ufs /dev/vinum/abyss'
I get this:
titan# fsck -t ufs /dev/vinum/abyss
** /dev/vinum/abyss
CANNOT READ BLK:
I have mailed about this problem a few times now, and I have got
responses from Greg very quick where he asks for more information, but
I never get any replies on my replies. This makes me worried that I'm
doing something wrong or that I appear to be rude, something I
certainly don't want to be,
This is an old thread, that I have cleaned up to maybe get an answer.
*
What problems are you having?
One of my drives are flagged down. Vinum reports that drive as
referenced. The other two drives in the RAID-5 is up.
According
to
vinum list my
After a power loss last night i restarted my server with a 425 gig or so
RAID-5 array and expected to go through a length fsck after which the
system would come up. However, one of the vinum subdisks was down. So,
i rebooted into single user mode, i restarted the home.p0.s3 subdisk and
then i
On Monday, 13 October 2003 at 23:46:12 -0700, Octavian Hornoiu wrote:
After a power loss last night i restarted my server with a 425 gig or so
RAID-5 array and expected to go through a length fsck after which the
system would come up. However, one of the vinum subdisks was down. So,
i
13 matches
Mail list logo
