On Mar 23, 2014, at 11:32 AM, Reginald Beardsley <[email protected]> wrote:

> I'm not aware of any TB+ drives available w/ 512b sectors.  An RMA by HGST of 
> a 512b drive got me a 4kb sector replacement.  I was informed that getting a 
> 512b sector replacement drive was not possible.  My experience is that except 
> for small drives, 512b sector drives are already unobtainable.

This sounds like SATA disks. HGST 4TB SATA disks are 4K, SAS are 512n. The SAS 
storage vendors often have requirements like 520 byte sectors, that don't match
the 4K SATA world (SATA cannot do 520 byte sectors)

> 
> I think the issue Alexander encountered is in part the result of drives lying 
> to the installer.
>  In looking at my notes from installing oi151a7 on an N40L I seem to have had 
> trouble w/ the text installer.

The installed knows nothing about the physical block size, nor does it care.

More below...

>   Ultimately I succeeded using the LiveDVD GUI installer by installing to a 
> small temporary partition, then manually creating a partition on another 
> disk, forming a mirror and after it silvered, breaking the mirror and redoing 
> the first partition and  reforming the mirror.  
> 
> However, in reading my notes it appears that I may have used a 512b disk for 
> the initial install, edited sd.conf, formed a pool on a partition of the 4kb 
> disk, formed the mirror and then removed the 512b disk and replaced it w/ a 
> 4kb disk. Unfortunately my notes are ambiguous.  I was also doing battle w/ 
> the 4kb HGST drive on my Sol 10 system and having other entertainment w/ a 
> 4kb USB drive.
> 
> I remember feeling pretty beat up by the time I was done.  I got things as I 
> wanted them, but it was quite painful.  format(1m) would create partitions 
> which were not sector aligned. or complain that they weren't when they were.
> 
> It *can* be done, but forcing correct alignment of the pool can be difficult. 
>  I *really* wish one could just tell zpool to ignore what the disk says and 
> force ashift=12 or whatever is desired.
> 
> I hope this offers some clues.
> Reg 
> 
> 
> --------------------------------------------
> On Sun, 3/23/14, Richard Elling <[email protected]> wrote:
> 
> Subject: Re: [discuss] rpool -- ashift=12 possible?
> To: "[email protected]" <[email protected]>
> Date: Sunday, March 23, 2014, 12:15 PM
> 
> 
>> On Mar 23, 2014, at 6:13 AM, Alexander Lesle <[email protected]>
> wrote:
>> 
>> Hello All
>> 
>> In the near future we can only buy drives with
>> physical block sizes 4096b and greater.
>> Drives with 512b are EOL.
> 
> This date is many years in the future.
> 
>> 
>> Here in the wiki 
>> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks
>> Jim Klimov reported.
>> In the list of AF drives we can found a lot of drives,
> but the list is
>> IMHO not complete.
>> I want to install it on a Kingston SSDnow 200/30GB
>> This are the informations I need:
>> root@arche:~#
>> root@arche:~# iostat -Er | grep -i vendor | sort |
> uniq
>> Vendor: ATA      ,Product: KINGSTON
> SS200S3 ,Revision: 05.1 ,Serial No: xxxxx
>> root@arche:~#
>> root@arche:~# echo ::sd_state | mdb -k | egrep
> '(^un|_blocksize)'
>> un 0: ffffff04e92926c0
>>     un_sys_blocksize = 0x200
>>     un_tgt_blocksize = 0x200
>>     un_phy_blocksize = 0x1000

This is the critical information -- the disk is not lying about its
physical block size... unless this is taken after you forced the
physical block size with sd.conf overrides.

>>     un_f_tgt_blocksize_is_valid = 0x1

un_f_tgt_blocksize_is_valid has nothing to do with this issue.

>> un 1: 0
>> ...
>> ...
>> root@arche:~#
>> 
>> When I installing Omnios on this SSD the installer make
> rpool
>> only ashift=9 and not ashift=12 or 13 itself.
> 
> I believe your analysis is faulty. There is no way to force
> a pool to 512 or 4k. If the pool is 512, then that is the
> reported phys block size at the time.

The reason I hold this stance is because the info above shows
the proper physical block size is detected and that is what zpool
create uses.

Question: is this the physical block size reported by the system
prior to running the installer? If not, then we know how to change
that...
 -- richard

> 
> 
>   -- richard
> 
>> Ok, new installation going to CLI and instert:
>> ,-----[sd.conf]-----
>> | sd-config-list =
>> |       "ATA 
>    Samsung SSD 840 ",
> "physical-block-size:8192",
>> |       "ATA 
>    Kingston SS200S3",
> "physical-block-size:4096";
>> `-------------------
>> Exit CLI and follow the standard installation procedure
> with 'F2'.
>> After reboot from SSD I get a warning on Console:
>> ,-----[CLI]-----
>> | WARNING: Disk, '/dev/dsk/c3t0d0s0', has a block
> alignment that is
>> | larger than the pool's alignment
>> `-------------------
>> rpool ist not what I want.
>> root@arche:~#
>> root@arche:~# zdb | egrep 'ashift| name'
>>     name: 'rpool'
>>             ashift: 9
>> When deleting the upper entry in sd.conf no Message
> appear any more.
>> 
>> Question:
>> Must rpool set ashift=9 independent on the drive?
>> Depends on the omnios installer?
>> Is there a way to install rpool with ashift=12 or 13?
>> 
>> Thx in advance.
>> -- 
>> Best Regards
>> Alexander
>> März, 23 2014
>> 
>> 
>> 
>> -------------------------------------------
>> illumos-discuss
>> Archives: https://www.listbox.com/member/archive/182180/=now
>> RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175743-23d1427b
>> Modify Your Subscription: https://www.listbox.com/member/?&;
>> Powered by Listbox: http://www.listbox.com
> 
> 
> -------------------------------------------
> illumos-discuss
> Archives: https://www.listbox.com/member/archive/182180/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/182180/23998448-902cecc3
> Modify Your Subscription: https://www.listbox.com/member/?&;
> Powered by Listbox: http://www.listbox.com
> 
> 
> 
> -------------------------------------------
> illumos-discuss
> Archives: https://www.listbox.com/member/archive/182180/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175743-23d1427b
> Modify Your Subscription: https://www.listbox.com/member/?&;
> Powered by Listbox: http://www.listbox.com



-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to