Well, what I was looking for is what the physical drive without any
prodding from sd.conf would respond...
On 2013-03-20 14:21, Reginald Beardsley wrote:
FWIW
This is how and shows what an ST2000DM001 properly configured using sd.conf
reports:
oi%rhb {2} echo "::sd_state" | mdb -k | egrep '^un|blocksize'
un 0: ffffff0140ddfd00
un_sys_blocksize = 0x200
un_tgt_blocksize = 0x200
un_phy_blocksize = 0x1000
un_f_tgt_blocksize_is_valid = 1
0x200 = 512 bytes
0x1000 = 4096 bytes
Have Fun!
Reg
--- On Wed, 3/20/13, Hans J. Albertsson <hans.j.alberts...@branneriet.se> wrote:
From: Hans J. Albertsson <hans.j.alberts...@branneriet.se>
Subject: [OpenIndiana-discuss] How can one test in situ, and under OI, the
physical blocksize a SATA disk actually reports??
To: openindiana-discuss@openindiana.org
Date: Wednesday, March 20, 2013, 8:05 AM
I absolutely need such a tool. Don't
ask... ah well, to impress a silly would-be colleague.
I tried parted and gparted and a few others: but I can't
seem to make them report what I want to know.
cfgadm, luxadm, ....???
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
