FreeBSD bugmaster | 3 Oct 13:02 2005
Picon

Current problem reports assigned to you

Current FreeBSD problem reports
Critical problems
Serious problems
Non-critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
o [2005/02/26] bin/78131   geom        gbde "destroy" not working.
o [2005/03/26] kern/79251  geom        [2TB] newfs fails on 2.6TB gbde device

2 problems total.

Joshua Bell | 6 Oct 19:52 2005
Picon

GEOM's RAID level support

I am sorry if this is covered in areas I was unable to view.  But, from what it looks like GEOM is limited to 0/1
raid levels.  Basically, what I am needing is a raid5 configuration from bootstrap.  Any information that
can be provided towards suggested solutions for this, is greatly appriciated.

-Josh
Dag-Erling Smørgrav | 6 Oct 21:01 2005
Picon

Re: GEOM's RAID level support

Joshua Bell <josh <at> oplink.net> writes:
> I am sorry if this is covered in areas I was unable to view.  But,
> from what it looks like GEOM is limited to 0/1 raid levels.
> Basically, what I am needing is a raid5 configuration from
> bootstrap.

You can't boot from a RAID 5 volume without hardware support.

DES
--

-- 
Dag-Erling Smørgrav - des <at> des.no

Danny Howard | 6 Oct 22:08 2005

Re: GEOM's RAID level support

On Thu, Oct 06, 2005 at 09:01:36PM +0200, Dag-Erling Sm?rgrav wrote:
> Joshua Bell <josh <at> oplink.net> writes:
> > I am sorry if this is covered in areas I was unable to view.  But,
> > from what it looks like GEOM is limited to 0/1 raid levels.
> > Basically, what I am needing is a raid5 configuration from
> > bootstrap.
> 
> You can't boot from a RAID 5 volume without hardware support.

Has anyone a recipe for a RAID1,0 bootstrap? :)

-danny
Pawel Jakub Dawidek | 6 Oct 22:16 2005
Picon

Re: GEOM's RAID level support

On Thu, Oct 06, 2005 at 01:08:02PM -0700, Danny Howard wrote:
+> On Thu, Oct 06, 2005 at 09:01:36PM +0200, Dag-Erling Sm?rgrav wrote:
+> > Joshua Bell <josh <at> oplink.net> writes:
+> > > I am sorry if this is covered in areas I was unable to view.  But,
+> > > from what it looks like GEOM is limited to 0/1 raid levels.
+> > > Basically, what I am needing is a raid5 configuration from
+> > > bootstrap.
+> > 
+> > You can't boot from a RAID 5 volume without hardware support.
+> 
+> Has anyone a recipe for a RAID1,0 bootstrap? :)

Forget it. Everything which splits the data across disks will not work.
With software RAID you can operate on disks, slices, partitions, etc.
no limits here. I'd suggest creating small RAID1 on top of small
partitions for the root file system (or at least for /boot/ directory,
which is minimum).

--

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd <at> FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
Danny Howard | 6 Oct 22:27 2005

Re: GEOM's RAID level support

On Thu, Oct 06, 2005 at 10:16:16PM +0200, Pawel Jakub Dawidek wrote:
> On Thu, Oct 06, 2005 at 01:08:02PM -0700, Danny Howard wrote:

> +> Has anyone a recipe for a RAID1,0 bootstrap? :)
> 
> Forget it. Everything which splits the data across disks will not work.
> With software RAID you can operate on disks, slices, partitions, etc.
> no limits here. I'd suggest creating small RAID1 on top of small
> partitions for the root file system (or at least for /boot/ directory,
> which is minimum).

Well, I have RAID1 systems ...

It seems reasonable to conclude that one could set up / as a RAID1 on
the first pair of disks, and bootstrap far enough to include swap, /var,
and /usr from a RAID10 stretched across a full-disk set.  It just sounds
somewhat tricky to set it all up, is all, so if someone has grokked out
a recipe ... :)

-danny

Pawel Jakub Dawidek | 6 Oct 22:40 2005
Picon

Re: GEOM's RAID level support

On Thu, Oct 06, 2005 at 01:27:00PM -0700, Danny Howard wrote:
+> On Thu, Oct 06, 2005 at 10:16:16PM +0200, Pawel Jakub Dawidek wrote:
+> > On Thu, Oct 06, 2005 at 01:08:02PM -0700, Danny Howard wrote:
+> 
+> > +> Has anyone a recipe for a RAID1,0 bootstrap? :)
+> > 
+> > Forget it. Everything which splits the data across disks will not work.
+> > With software RAID you can operate on disks, slices, partitions, etc.
+> > no limits here. I'd suggest creating small RAID1 on top of small
+> > partitions for the root file system (or at least for /boot/ directory,
+> > which is minimum).
+> 
+> Well, I have RAID1 systems ...
+> 
+> It seems reasonable to conclude that one could set up / as a RAID1 on
+> the first pair of disks, and bootstrap far enough to include swap, /var,
+> and /usr from a RAID10 stretched across a full-disk set.  It just sounds
+> somewhat tricky to set it all up, is all, so if someone has grokked out
+> a recipe ... :)

This is one of mine setups (5 SATA disks):

beast:root:~# df -h -t ufs
Filesystem          Size    Used   Avail Capacity  Mounted on
/dev/mirror/root    1.9G    228M    1.6G    13%    /
/dev/raid3/usr      3.9G    1.9G    1.7G    53%    /usr
/dev/raid3/data     570G     99G    425G    19%    /usr/home

beast:root:~# graid3 status
      Name    Status  Components
(Continue reading)

Adrian Wontroba | 8 Oct 03:35 2005
Picon

Re: GEOM's RAID level support

On Thu, Oct 06, 2005 at 01:27:00PM -0700, Danny Howard wrote:

> Well, I have RAID1 systems ...

I've just reworked one of my home systems, doubling its disk capacity.

I started with a pretty standard gmirrored two disk system, added
another Promise controller and another pair of (nearly) identical disks,
setting up the new disks as:

Mirrored root (gm0).
Single plex mirror of swap (gm1) or Single plex mirror of /var and /usr (gm2)
Rest of the space striped (gs0), underneath a single plex mirror of /home (gm3)

When I'd got the new mirrors working, I manually amended /etc/fstab etc,
booted from them and setup the other stripes/ plexes on the original
disks, ending up with four plexes for /root and two for everything
else. With the ATA write cache enabled it flies. With the write cache
disabled it crawls. Must buy a UPS.

The end result looks like:

bash-2.05b# gmirror status
      Name    Status  Components
mirror/gm0  COMPLETE  ad4a
                      ad6a
                      ad8a
                      ad10a
mirror/gm1  COMPLETE  ad4d
                      ad8d
(Continue reading)

Pawel Jakub Dawidek | 8 Oct 08:57 2005
Picon

Re: GEOM's RAID level support

On Sat, Oct 08, 2005 at 02:35:21AM +0100, Adrian Wontroba wrote:
+> The end result looks like:
+> 
+> bash-2.05b# gmirror status
+>       Name    Status  Components
+> mirror/gm0  COMPLETE  ad4a
+>                       ad6a
+>                       ad8a
+>                       ad10a

Isn't that waste of space?
I see your /var/ file system is the same size as / file system, so
creating two mirrors (ad4a+ad6a) for / and (ad8a+ad10a) for /var/ will
save you some space.

+> I set the system up with a Makefile and some initial disk labels
+> (below my sig) and lots of trial and error, executing make zap, make
+> label_disks, etc.  No doubt less than perfect, but it worked for me.
+> 
+> At work, I've developed a makefile based version of RSE's "single disk
+> to two disk" approach.  If there is any interest, I'll ask my boss if I
+> can release it.

Nice idea, but I think at this point it is too much specific for you
configuration. It'd be much useful when it will be more general somehow.

+> Is anybody doing anything about:
+> Making systinstall GEOM aware?

Yes, Craig Rodrigues (rodrigc <at> ) is working on it.
(Continue reading)

Adrian Wontroba | 9 Oct 19:36 2005
Picon

Re: GEOM's RAID level support

On Sat, Oct 08, 2005 at 08:57:51AM +0200, Pawel Jakub Dawidek wrote:
> On Sat, Oct 08, 2005 at 02:35:21AM +0100, Adrian Wontroba wrote:
> +> mirror/gm0  COMPLETE  ad4a
> +>                       ad6a
> +>                       ad8a
> +>                       ad10a
> 
> Isn't that waste of space?

Yes, but it isn't a lot of space (1 GB on each of four 150 GB disks),
and it gives me the comfort blanket of being able to boot from any disk.

> +> At work, I've developed a makefile based version of RSE's "single disk
> +> to two disk" approach.  If there is any interest, I'll ask my boss if I
> +> can release it.

> Nice idea, but I think at this point it is too much specific for you
> configuration. It'd be much useful when it will be more general somehow.

The makefile I produced at work is much more general. Provided the first
disk is no larger than the second, and contains a single *s1 slice, it
will build an two disk system equivalent to the first, with the same
partition sizes. It also has a fall back for the "almost the same size
but different geometry" gotcha. I hate this ancient CHS cruft.

It is being used soon after sysinstall by UNIX novices.  Of course, it
will probably be totally redundant once Craig makes sysinstall GEOM
aware.

--

-- 
(Continue reading)


Gmane