search for: sd9

...d4 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd5 0.0 118.0 0.0 15099.9 0.0 35.0 296.7 0 100 sd6 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd7 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd8 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd9 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd10 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd11 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd12 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd13 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sd1...

...i=on with 2 thin provisioned partitions of 1TB each (zfs create -s -V 1tb idrive/d1). Access to the shares with an iscsi initiator was successful, all was smooth, until the reboot. Upon reboot, the console reports the following errors. WARNING: /scsi_vhci/disk at g0100015c55fb40900002a00483e34c6 (sd9): disk has 3221225472 blocks, which is too large for a 32-bit kernel WARNING: /iscsi/disk at 0000iqn.1986-03.com.sun%3A02%3Aee2143f2-f5ce-6414-fcda-8035dacfc3730001,0 (sd10): disk has 3221225472 blocks, which is too large for a 32-bit kernl And it continues to do this on the other partitio...

...445.7 0.0 46239.2 0.0 0.0 6.6 14.7 0 79 sd7 452.7 0.0 46850.7 0.0 0.0 6.0 13.3 0 79 sd8 460.7 0.0 46947.7 0.0 0.0 5.5 11.8 0 73 sd3 426.7 0.0 43726.4 0.0 5.6 0.8 14.9 73 79 sd5 424.7 0.0 44456.4 0.0 6.6 0.9 17.7 83 90 sd9 430.7 0.0 44266.5 0.0 5.8 0.8 15.5 78 84 sd10 421.7 0.0 44451.4 0.0 6.3 0.9 17.1 80 87 sd11 421.7 0.0 44196.1 0.0 5.8 0.8 15.8 75 80 capacity operations bandwidth pool used avail read write read write ---------- --...

I have just recently (physically) moved a system with 16 hard drives (for the array) and 1 OS drive; and in doing so, I needed to pull out the 16 drives so that it would be light enough for me to lift. When I plugged the drives back in, initially, it went into a panic-reboot loop. After doing some digging, I deleted the file /etc/zfs/zpool.cache. When I try to import the pool using the zpool

Hello everyone, As one of the steps of improving my ZFS home fileserver (snv_134) I wanted to replace a 1TB disk with a newer one of the same vendor/model/size because this new one has 64MB cache vs. 16MB in the previous one. The removed disk will be use for backups, so I thought it''s better off to have a 64MB cache disk in the on-line pool than in the backup set sitting off-line all

Under Solaris 10 u6 , No matter how I configured my ARECA 1261ML Raid card I got errors on all drives that result from SCSI timeout errors. yoda:~ # tail -f /var/adm/messages Jan 9 11:03:47 yoda.asc.edu scsi: [ID 107833 kern.notice] Requested Block: 239683776 Error Block: 239683776 Jan 9 11:03:47 yoda.asc.edu scsi: [ID 107833 kern.notice] Vendor: Seagate

G''day, all, So, I''ve decided to migrate my home server from Linux+swRAID+LVM to Solaris+ZFS, because it seems to hold much better promise for data integrity, which is my primary concern. However, naturally, I decided to do some benchmarks in the process, and I don''t understand why the results are what they are. I though I had a reasonable understanding of ZFS, but now

Test =) soddsjbmshdwqwu -- Test, yep.

...41:20 san sata: [ID 514995 kern.info] SATA Gen1 signaling speed (1.5Gbps) Jan 17 06:41:20 san sata: [ID 349649 kern.info] Supported queue depth 32 Jan 17 06:41:20 san sata: [ID 349649 kern.info] capacity = 1953525168 sectors Jan 17 06:41:20 san scsi: [ID 193665 kern.info] sd9 at marvell88sx2: target 4 lun 0 Jan 17 06:41:20 san genunix: [ID 936769 kern.info] sd9 is /pci at 0,0/pci10de,376 at a/pci1033,125 at 0,1/pci11ab,11ab at 6/disk at 4,0 Jan 17 06:41:20 san genunix: [ID 408114 kern.info] /pci at 0,0/pci10de,376 at a/pci1033,125 at 0,1/pci11ab,11ab at 6/disk at 4,0...