Re: question on vinum

From: secmgr (security_at_jim-liesl.org)
Date: 10/28/04

  • Next message: freebsd-stable_at_auscert.org.au: "php5 port compile problem"
    Date: Thu, 28 Oct 2004 15:39:34 -0600
    To: Marko Raiha <mjraiha@fade.pp.fi>
    
    

    Marko Raiha wrote:

    >Hi,
    >
    >On Wed, Oct 27, 2004 at 09:10:39AM -0600, secmgr wrote:
    >
    >
    >>The reason is empirically derived. When I created a 7 disk raid 5 set
    >>using "len 0" or all the space available, the raid set would be corrupt
    >>after initializing. Every time. When I reserved back that extra
    >>space, no corruption.
    >>(freebsd 4.10-p3) There was a thread on this a few days ago.
    >>
    >>
    >
    >Thanks about pointing to this another thread. I read the thread and one
    >thing is still a bit unclear. Do you mean by leaving 64 blocks unused to
    >leave it unused at the beginning of disk before vinum partition (when
    >doing partition to vinum by disklabeling freebsd slice) like this:
    >
    ># /dev/aacd2s1:
    >8 partitions:
    ># size offset fstype [fsize bsize bps/cpg]
    > c: 143347932 0 unused 0 0
    > h: 143347868 64 vinum
    >
    >or somewhere in subdisk as you said? I guess that inadvertently not
    >right terms were used ("subdisk" instead of "disk"), because terminology
    >with vinum is a bit complicated.
    >
    >All documentations I have found says that only 16 block should be left
    >unused at the beginning of the disk like this:
    >
    ># /dev/aacd2s1:
    >8 partitions:
    ># size offset fstype [fsize bsize bps/cpg]
    > c: 143347932 0 unused 0 0
    > h: 143347916 16 vinum
    >
    >Regards,
    >
    >
    That probably would have worked too. My mistake was to clone the c
    partition entry, call it h, label it vinum, and use that
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: freebsd-stable_at_auscert.org.au: "php5 port compile problem"

    Relevant Pages

    • Re: Vinum dumpconfig returns nothing ?!?
      ... A little googling for Disklabel and I was ... So if you mess up your partition tables, ... (replacing rad1 by the raw device name of your disk). ... > vinum in order to avoid overwriting data used for other purposes. ...
      (freebsd-current)
    • Re: Vinum Offset for Swap: 265 or 281?
      ... modify swap partition size to be 281 less than what sysinstall ... have the swap offset at 281 instead of 0 ... add vinum partition set to the size of "c" minus 16 ... Should the subdisk offset be equal to the partition offset? ...
      (freebsd-questions)
    • Re: vinum problems
      ... >I've just built a machine with a vinum root successfully. ... >the primary disk with no problems but any attempt to start the mirror ... vinum root partition is really useless. ...
      (freebsd-questions)
    • Re: Vinum dumpconfig returns nothing ?!?
      ... These are disk devices, not disk partitions. ... vinum in order to avoid overwriting data used for other purposes. ... Partition ``b'' is a swap partition, ... drives unless they were a partition of type "vinum". ...
      (freebsd-current)
    • Re: Vinum + new disk for mirror
      ... I was hoping that it would copy the partition table ... The Vinum config would, indeed, get copied. ... make the partition table to cover the entire disk. ... I may ignore the reply or reply to the original recipients. ...
      (freebsd-questions)