Re: ciss(4) not coping with large arrays?
Running today's RELENG_7 (although 7.0-RELEASE has the same problem), GENERIC kernel on an amd64 and I can't seem to get a da(4) device for any arrays bigger than 2TB. In earlier releases (5 and 6 at least) you couldn't create partitions larger than 2 TB. I don't know whether work has been to circumvent this in 7 but tools like fsck has to be changed as well. Have you tried zfs? dmesg: ... ciss0: HP Smart Array P400 port 0x4000-0x40ff mem 0xfdf0-0xfdff,0xfdef -0xfdef0fff irq 16 at device 0.0 on pci10 ciss0: [ITHREAD] ... da0 at ciss0 bus 0 target 0 lun 0 da0: COMPAQ RAID 1 VOLUME OK Fixed Direct Access SCSI-5 device da0: 135.168MB/s transfers da0: 953837MB (1953459632 512 byte sectors: 255H 32S/T 65535C) da1 at ciss0 bus 0 target 1 lun 0 da1: COMPAQ RAID 0 VOLUME OK Fixed Direct Access SCSI-5 device da1: 135.168MB/s transfers da1: 953837MB (1953459632 512 byte sectors: 255H 32S/T 65535C) da2 at ciss0 bus 0 target 2 lun 0 da2: COMPAQ RAID 0 VOLUME OK Fixed Direct Access SCSI-5 device da2: 135.168MB/s transfers da2: 1907675MB (3906918832 512 byte sectors: 255H 32S/T 65535C) (da3:ciss0:0:3:0): got CAM status 0x4 (da3:ciss0:0:3:0): fatal error, failed to attach to device (da3:ciss0:0:3:0): lost device (da3:ciss0:0:3:0): removing device entry (da4:ciss0:0:4:0): got CAM status 0x4 (da4:ciss0:0:4:0): fatal error, failed to attach to device (da4:ciss0:0:4:0): lost device (da4:ciss0:0:4:0): removing device entry ... The arrays I'm testing with: da1 = 1 x 1TB da2 = 2 x 1TB da3 = 3 x 1TB da4 = 4 x 1TB Also: # camcontrol devlist COMPAQ RAID 1 VOLUME OK at scbus0 target 0 lun 0 (pass0,da0) COMPAQ RAID 0 VOLUME OK at scbus0 target 1 lun 0 (pass1,da1) COMPAQ RAID 0 VOLUME OK at scbus0 target 2 lun 0 (pass2,da2) COMPAQ RAID 0 VOLUME OK at scbus0 target 3 lun 0 (pass3) COMPAQ RAID 0 VOLUME OK at scbus0 target 4 lun 0 (pass4) # camcontrol readcap pass2 Last Block: 3906918831, Block Length: 512 bytes # camcontrol readcap pass3 (pass3:ciss0:0:3:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0 (pass3:ciss0:0:3:0): CAM Status: CCB request completed with an error Is it possible to get FreeBSD to recognize arrays 2TB? Are there any further diagnostics I can provide? --Emil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ciss(4) not coping with large arrays?
On Fri, May 16, 2008 at 1:03 AM, Paul Saab [EMAIL PROTECTED] wrote: On Fri, May 16, 2008 at 12:50 AM, Claus Guttesen [EMAIL PROTECTED] wrote: Running today's RELENG_7 (although 7.0-RELEASE has the same problem), GENERIC kernel on an amd64 and I can't seem to get a da(4) device for any arrays bigger than 2TB. In earlier releases (5 and 6 at least) you couldn't create partitions larger than 2 TB. I don't know whether work has been to circumvent this in 7 but tools like fsck has to be changed as well. Have you tried zfs? zfs has nothing to do with this. The driver is not properly dealing with the large volume. set the kernel tunable in loader.conf kern.cam.da.3.minimum_cmd_size=16 kern.cam.da.4.minimum_cmd_size=16 Actually, this has nothing to do with it either.. Please try the following patch: http://yogurt.org/FreeBSD/ciss_large.diff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ciss(4) not coping with large arrays?
On Fri, May 16, 2008 at 12:50 AM, Claus Guttesen [EMAIL PROTECTED] wrote: Running today's RELENG_7 (although 7.0-RELEASE has the same problem), GENERIC kernel on an amd64 and I can't seem to get a da(4) device for any arrays bigger than 2TB. In earlier releases (5 and 6 at least) you couldn't create partitions larger than 2 TB. I don't know whether work has been to circumvent this in 7 but tools like fsck has to be changed as well. Have you tried zfs? zfs has nothing to do with this. The driver is not properly dealing with the large volume. set the kernel tunable in loader.conf kern.cam.da.3.minimum_cmd_size=16 kern.cam.da.4.minimum_cmd_size=16 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ciss(4) not coping with large arrays?
On Fri, May 16, 2008 at 01:19:33AM -0700, Paul Saab wrote: Emil: Running today's RELENG_7 (although 7.0-RELEASE has the same problem), GENERIC kernel on an amd64 and I can't seem to get a da(4) device for any arrays bigger than 2TB. Please try the following patch: http://yogurt.org/FreeBSD/ciss_large.diff This works a treat! da4 at ciss0 bus 0 target 4 lun 0 da4: COMPAQ RAID 0 VOLUME OK Fixed Direct Access SCSI-5 device da4: 135.168MB/s transfers da4: 3815350MB (7813837232 512 byte sectors: 255H 32S/T 65535C) Double thanks for committing it, and for merging to RELENG_7! --Emil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
