dm == David Magda dma...@ee.ryerson.ca writes:
dm The other thing is that with the growth of SSDs, if more OS
dm vendors support dynamic sectors, SSD makers can have
dm different values for the sector size
okay, but if the size of whatever you're talking about is a multiple
of 512,
Brandon High writes:
On Tue, Nov 23, 2010 at 9:55 AM, Krunal Desai mov...@gmail.com wrote:
What is the upgrade path like from this? For example, currently I
The ashift is set in the pool when it's created and will persist
through the life of that pool. If you set it at pool creation,
kd == Krunal Desai mov...@gmail.com writes:
kd http://support.microsoft.com/kb/whatever
dude.seriously?
This is worse than a waste of time. Don't read a URL that starts this
way.
kd Windows 7 (even with SP1) has no support for 4K-sector
kd drives.
NTFS has 4KByte allocation
On 12/01/10 22:14, Miles Nordin wrote:
Also did anyone ever clarify whether the slog has an ashift? or is it
forced-512? or derived from whatever vdev will eventually contain the
separately-logged data? I would expect generalized immediate Caring
about that since no slogs except ACARD and
I'd also note that in the future at some point, we won't be able to purchase
512B drives any more. In particular, I think that 3TB drives will all be 4KB
formatted. So it isn't inadvisable for a pool that you plan on expanding to
have ashift=12 (imo).
One new thought occurred to me; I know
On 27 November 2010 08:05, Krunal Desai mov...@gmail.com wrote:
One new thought occurred to me; I know some of the 4K drives emulate 512
byte sectors, so to the host OS, they appear to be no different than other
512b drives. With this additional layer of emulation, I would assume that
ashift
On Nov 26, 2010, at 20:09 , taemun wrote:
If you consider that for a 4KB internal drive, with a 512B external
interface, a request for a 512B write will result in the drive reading 4KB,
modifying it (putting the new 512B in) and then writing the 4KB out again.
This is terrible from a
On Tue, Nov 23, 2010 at 9:55 AM, Krunal Desai mov...@gmail.com wrote:
What is the upgrade path like from this? For example, currently I
The ashift is set in the pool when it's created and will persist
through the life of that pool. If you set it at pool creation, it will
stay regardless of OS
zdb -C shows an shift value on each vdev in my pool, I was just wondering if
it is vdev specific, or pool wide. Google didn't seem to know.
I'm considering a mixed pool with some advanced format (4KB sector)
drives, and some normal 512B sector drives, and was wondering if the ashift
can be set
On Tue, November 23, 2010 08:53, taemun wrote:
zdb -C shows an shift value on each vdev in my pool, I was just wondering
if it is vdev specific, or pool wide. Google didn't seem to know.
I'm considering a mixed pool with some advanced format (4KB sector)
drives, and some normal 512B sector
Interesting, I didn't realize that Soracle was working on/had a
solution somewhat in place for 4K-drives. I wonder what will happen
first for me, Hitachi 7K2000s hitting a reasonable price, or
4K/variable-size sector support hiting so I can use Samsung F4s or
Barracuda LPs.
On Tue, Nov 23, 2010
Cheers for the links David, but you'll note that I've commented on the blog
you linked (ie, was aware of it). The zpool-12 binary linked from
http://digitaldj.net/2010/11/03/zfs-zpool-v28-openindiana-b147-4k-drives-and-you/
worked
perfectly on my SX11 installation. (It threw some error on b134, so
On Tue, Nov 23, 2010 at 9:59 AM, taemun tae...@gmail.com wrote:
I'm currently populating a pool with a 9-wide raidz vdev of Samsung HD204UI
2TB (5400rpm, 4KB sector) and a 9-wide raidz vdev of Seagate LP ST32000542AS
2TB (5900 rpm, 4KB sector) which was created with that binary, and haven't
13 matches
Mail list logo
