Re: vinum question
From: Karl E. Taylor (ktayloraz_at_qwest.net)
Date: 07/16/04
- Next message: james
hal-pc.org: "Re: about setting IRQ:s for nics" - Previous message: Karl E. Taylor: "Re: vinum question"
- In reply to:(deleted message) John Doherty: "Re: vinum question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 16 Jul 2004 07:53:40 -0700
John Doherty wrote:
> In article <40f03c72$0$64297$4c5eba9e@news.getnet.net>, "Karl E. Taylor"
> <ktayloraz@qwest.net> wrote:
>
>
>>When I boot, and yes I have start_vinum="YES" in my rc.conf. However,
>>for some silly reason, when I boot, the volume is gone, and of course
>>this cause the system to go into the /bin/sh and try to get me to do an
>>fsck on the missing volume.
>
>
> What exactly have you put in /etc/fstab for this file system?
>
>
>>I have a file named /etc/config1.vinum, that I use to recreate the
>>volume after boot up
>
>
> You shouldn't have to do that. The configuration is stored on the
> disks themselves and there is no config file, per se. And if
> everything is configured correctly and working at that point, you
> should just be able to mount the file system, without needing to
> recreate the vinum configuration.
>
> Once the volume is mounted, what is listed in the output of "df"?
>
> As someone else mentioned, it's possible that the disks aren't
> spinning up quickly enough. That's not too likely, I don't think,
> but if it's a problem, you can build a new kernel with a longer
> SCSI_DELAY value to give them more time.
>
> --
Yeah, I agree, but for some bizzar reason, it did not write to these
disks. Oh, the volume is there when I run vinum create
/etc/config1.vinum, but it won't write the config data to the disks
after that. Even with all the save commands and blah blah blah.
So, in rc.local, I created the startup, and it works great. I admit,
it's the WRONG way to do it, but the joy of UNIX is, there is always at
least 3 ways to do something.
It's probably because of the types of disks or the server it's self. I
have a similar server running Solaris 2.9x86, and when the disks spin up
there, I get bad opcode errors on each disk. But the server runs fine
once booted.
-- Dr. Karl E. Taylor UNIX Systems Administrator / Oracle DBA
- Next message: james
hal-pc.org: "Re: about setting IRQ:s for nics" - Previous message: Karl E. Taylor: "Re: vinum question"
- In reply to:(deleted message) John Doherty: "Re: vinum question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|