seemed to work OK, so I'm not
> > certain. I wasn't willing to leave it that way to avoid wasting a little
> > space.
> > >
> > > I can't think of any reason that 512B drives wouldn't work fine aligned
> > to larger boundaries. The only con
an issue given we're talking pennies per GB. I can't
> imagine a performance issue that could result.
> >
> > It seems to me that the default alignment rules would give less trouble
> if the alignment was to the most restrictive requirement.
> >
> > -
I think a wiki update is in order. As simple an idea as it is, it was not
obvious to me to do that.
I'm sure this will come up again.
On Wed, 1/8/14, Bryan N Iotti wrote:
Subject: Re: [OpenIndiana-discuss] sd.conf trouble and illumos bug
B. I can't
> imagine a performance issue that could result.
>
> It seems to me that the default alignment rules would give less trouble if
> the alignment was to the most restrictive requirement.
>
> --------
> On Mon, 1/6/14, Bryan N
gine a
performance issue that could result.
It seems to me that the default alignment rules would give less trouble if the
alignment was to the most restrictive requirement.
----
On Mon, 1/6/14, Bryan N Iotti wrote:
Subject: Re: [OpenIndiana-discuss] sd
Hi Reginald,
Thanks for your reply.
In the end, I just booted from a live DVD and plugged that drive in on my
laptop using a double asterisk as the sd.conf line and an 8k block size. A test
pool create read back ashift=13, which should be fine.
Then I used format -e and fdisk to create a singl
I can't comment on your particular issue which is why I didn't respond earlier.
However, I had trouble getting a 3 TB Toshiba USB drive to work properly. I
spent a bunch of time reading the code that parses sd.conf, but finally gave up
and didn't go further.
On reflection I wonder if the pro
I'm bumping my own message here... ;)
Any hints at all?
Does it have something to do with being connected to an LSI SAS1064E-based
controller?
Again, sorry for bumping, but I hate having that disk just lying there,
unused...
Bryan
On Fri, 3 Jan 2014 23:01:15 +0100
Bryan N Iotti wrote:
Hi all,
I recently acquired a consumer 128 GB SanDisk SATA SSD to replace my root pool
disks.
I anticipated having to enter the VID and PID into sd.conf as with other 4K or
higher drives.
Unfortunately, no matter what I enter there, the drive retains the 512 byte
block size and ashift remains