Re: Dell PERC6?

2008-01-23 Thread Aldas Nabazas
On Jan 23, 2008 1:58 PM, John Baldwin [EMAIL PROTECTED] wrote:

 On Sunday 20 January 2008 09:50:36 am Jeremy Chadwick wrote:
  On Fri, Jan 18, 2008 at 10:35:21AM +0100, Ferdinand Goldmann wrote:
   Jeremy Chadwick wrote:
   You'd be best off with RELENG_7 and not 6.3, but yes, the controller
 in
   question should work on RELENG_6 and RELENG_6_3.
  
   Very well, seems like I am going to give RELENG_7 a try then.
   Thanks to everyone who replied!
 
  Another user just posted to -stable about problems with these Dell
  machines and PERC6.  I'm not sure if you're subscribed to -stable or
  not, so here's the thread:
 
 
 http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039791.html

 The problem folks are having are with using volumes greater than 1 TB.
  The
 BSD label cannot handle such large disks.  Instead, if you are just using
 the disk for data you can newfs /dev/mfid1 directly and use it as a
 filesystem, or if you need to partition the disk you can use gpt(8) to do
 so.  If you need to boot from such a large disk you will need to use the
 GPT boot code in HEAD (I will backport it to 6.x and 7.x soon).  I've
 successfully used it to boot on 2 TB mfi(4) volumes.  Unfortunately
 sysinstall doesn't support GPT at all, only the older MBR + BSD label
 method.

 Note that this problem has nothing to do with mfi(4) at all, but it is a
 limitation of the BSD label + MBR that applies to any volume = 2 TB.


Hi John,

It seems that the problem is exactly as you described as i was able to get
everything working setting 2x146 disks as RAID1 and 4x146 as RAID5.

Regards,
Aldas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Dell Perc 6 disk geometry problem with RAID5 (both 6.3 final and 7.0 RC1)

2008-01-23 Thread Aldas Nabazas
On Jan 23, 2008 2:19 PM, John Baldwin [EMAIL PROTECTED] wrote:

 On Sunday 20 January 2008 01:53:30 pm David Wood wrote:
  Hi there,
 
  In message [EMAIL PROTECTED], Erik
  Trulsson [EMAIL PROTECTED] writes
  On Sun, Jan 20, 2008 at 04:48:56PM +, David Wood wrote:
   In message [EMAIL PROTECTED]
 ,
   Aldas Nabazas [EMAIL PROTECTED] writes
   We bought a new Dell PowerEdge 2950III with Perc 6/i and have the
 disk
   geometry problem using 6.3 final or 7.0 RC1. Seems that we are not
 alone at
   least one guy has similar problem reported earlier:
  
  
 http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-01/msg0
  0506.html
  
  I do not know if the mfi(4) driver has any problems with large disks,
 but it
  is however well known that fdisk(8) and bsdlabel(8) (the tools normally
 used
  to partition disks) have problems with volumes larger than 2TB.
  
  If you want to use volumes larger than 2TB then gpt(8) is the
 recommended
  way to partition the disks.  It is however doubtful if the BIOS in your
  system will allow you to boot from a gpt(8) parttioned volume which is
  best solved with having a separate - smaller - boot volume where the OS
  itself is installed.
 
  Erik's reminder is timely for those with 2TB volumes.
 
  You must use gpt and not fdisk on any disk, be it a single drive (in the
  future, at least!) or a virtual disk on a RAID setup that are bigger
  than 2TB. It may be wise to use gpt on any virtual disk that you might
  grow to 2TB or larger in the future, so long as you're not needing to
  boot from that virtual disk.
 
  fdisk will not work properly with 2TB and larger volumes - the MBR /
  partition table setup can't cope with these large volumes.
 
 
  You can't boot from a GPT volume - that's a limitation of the BIOS
  architecture. There is some thought about using EFI on x64 hardware in
  the future (EFI is used on ia64 hardware; GPT is part of EFI), but we're
  not there yet. This isn't just about adding GPT support to the BIOS -
  the whole BIOS setup is wedded to MBR.
 
  If you need to boot from a 2TB array, create two virtual disks - one
  smaller than 2TB to boot from (and use MBR on that), then the residue
  can be GPT.

 Actually, using gptboot in HEAD you can now boot from GPT on large volumes
 (I've booted from a  2 TB volume on a PERC5 using mfi(4) with it).  I
 will see about getting that merged back to 6.x and 7.x in CVS.  We use
 it for large volumes on 6.x and all volumes on 7.x at work.

  When I said there was nothing relevant waiting for MFC, I was aware of
  the change that Tom mentioned, but that seems to be about Dell PERC 6
  being identified as such rather than a MegaRAID. It doesn't seem that it
  will change the behaviour of the driver in any way.

 In our testing at work the 2950 rev 3's worked fine with mfi(4).

 --
 John Baldwin


Hi John,

Nice to hear that.

Regards,
Aldas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Dell Perc 6 disk geometry problem with RAID5 (both 6.3 final and 7.0 RC1)

2008-01-20 Thread Aldas Nabazas
Hi,

We bought a new Dell PowerEdge 2950III with Perc 6/i and have the disk
geometry problem using 6.3 final or 7.0 RC1. Seems that we are not alone at
least one guy has similar problem reported earlier:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-01/msg00506.html

I was reading the mailing list and found that some of the people are happily
using this hardware with the latest FreeBSD:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039675.html

I just wonder what the status of mfi driver? Maybe it's not fully tested or
there will be some important fixes before 7.0 final? We are going to try
different RAID combinations but it definitely not working using 6x146GB as
RAID5.

Maybe someone could share the RAID combinations they successfully are
running on?

Thanks in advance.

Kind Regards,
Aldas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]