I have reason to believe that both the drive, and the OS are correct.
I have suspicion that the HBA simply handled the creation of this
volume somehow differently than how it handled the original. Don't
know the answer for sure yet.
Ok, that's confirmed now. Apparently when the drives ship
Your experience is exactly why I suggested ZFS start doing some right
sizing if you will. Chop off a bit from the end of any disk so that
we're guaranteed to be able to replace drives from different
manufacturers. The excuse being no reason to, Sun drives are always
of identical size. If
CR 6844090, zfs should be able to mirror to a smaller disk
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6844090
b117, June 2009
Awesome. Now if someone would only port that to solaris, I'd be a happy
man. ;-)
___
zfs-discuss mailing
On Sun, Apr 4, 2010 at 9:46 PM, Edward Ned Harvey solar...@nedharvey.comwrote:
CR 6844090, zfs should be able to mirror to a smaller disk
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6844090
b117, June 2009
Awesome. Now if someone would only port that to solaris, I'd be a
There is some question about performance. Is there any additional
overhead caused by using a slice instead of the whole physical device?
No.
If the disk is only used for ZFS, then it is ok to enable volatile disk
write caching
if the disk also supports write cache flush requests.
If
I haven't taken that approach, but I guess I'll give it a try.
From: Tim Cook [mailto:t...@cook.ms]
Sent: Sunday, April 04, 2010 11:00 PM
To: Edward Ned Harvey
Cc: Richard Elling; zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] To slice, or not to slice
On Sun, Apr 4, 2010
On Apr 4, 2010, at 8:11 PM, Edward Ned Harvey wrote:
There is some question about performance. Is there any additional
overhead caused by using a slice instead of the whole physical device?
No.
If the disk is only used for ZFS, then it is ok to enable volatile disk
write caching
if the
, which one(s) I want to
do, in order to create the large slice of my disks.
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
One reason to slice comes from recent personal experience. One disk
of
a mirror dies. Replaced under contract with an identical disk. Same
model number, same firmware. Yet when it's plugged into the system,
for an unknown reason, it appears 0.001 Gb smaller than the old disk,
and
- Edward Ned Harvey solar...@nedharvey.com skrev:
What build were you running? The should have been addressed by
CR6844090
that went into build 117.
I'm running solaris, but that's irrelevant. The storagetek array
controller
itself reports the new disk as infinitesimally smaller
And finally, if anyone has experience doing this, and process
recommendations? That is
My next task is to go read documentation
again, to refresh my memory from years ago, about the difference
between format, partition, label, fdisk, because those terms
dont have the same meaning
Oh, I managed to find a really good answer to this question. Several
sources all say to do precisely the same procedure, and when I did it
on a
test system, it worked perfectly. Simple and easy to repeat. So I
think
this is the gospel method to create the slices, if you're going to
On Apr 2, 2010, at 2:29 PM, Edward Ned Harvey wrote:
I've also heard that the risk for unexpected failure of your pool is
higher if/when you reach 100% capacity. I've heard that you should
always create a small ZFS filesystem within a pool, and give it some
reserved space, along with the
I would return the drive to get a bigger one before doing something as
drastic as that. There might have been a hichup in the production line,
and that's not your fault.
Yeah, but I already have 2 of the replacement disks, both doing the same
thing. One has a firmware newer than my old disk
On Sat, 3 Apr 2010, Edward Ned Harvey wrote:
I would return the drive to get a bigger one before doing something as
drastic as that. There might have been a hichup in the production line,
and that's not your fault.
Yeah, but I already have 2 of the replacement disks, both doing the same
On Fri, Apr 2, 2010 at 4:05 PM, Edward Ned Harvey
guacam...@nedharvey.comwrote:
Momentarily, I will begin scouring the omniscient interweb for
information, but I’d like to know a little bit of what people would say
here. The question is to slice, or not to slice, disks before using them in
On 03/04/2010 19:24, Tim Cook wrote:
On Fri, Apr 2, 2010 at 4:05 PM, Edward Ned Harvey
guacam...@nedharvey.com mailto:guacam...@nedharvey.com wrote:
Momentarily, I will begin scouring the omniscient interweb for
information, but I’d like to know a little bit of what people
would
On Sat, Apr 3, 2010 at 6:53 PM, Robert Milkowski mi...@task.gda.pl wrote:
On 03/04/2010 19:24, Tim Cook wrote:
On Fri, Apr 2, 2010 at 4:05 PM, Edward Ned Harvey guacam...@nedharvey.com
wrote:
Momentarily, I will begin scouring the omniscient interweb for
information, but I’d like to
On Sat, Apr 3, 2010 at 7:50 PM, Tim Cook t...@cook.ms wrote:
On Sat, Apr 3, 2010 at 6:53 PM, Robert Milkowski mi...@task.gda.plwrote:
On 03/04/2010 19:24, Tim Cook wrote:
On Fri, Apr 2, 2010 at 4:05 PM, Edward Ned Harvey
guacam...@nedharvey.com wrote:
Momentarily, I will begin
On Apr 3, 2010, at 5:56 PM, Tim Cook wrote:
On Sat, Apr 3, 2010 at 7:50 PM, Tim Cook t...@cook.ms wrote:
Your experience is exactly why I suggested ZFS start doing some right
sizing if you will. Chop off a bit from the end of any disk so that we're
guaranteed to be able to replace drives
.
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
ZFS storage and performance consulting at http://www.RichardElling.com
ZFS training on deduplication, NexentaStor, and NAS performance
Las Vegas, April 29-30, 2010
On Sat, Apr 3, 2010 at 9:52 PM, Richard Elling richard.ell...@gmail.comwrote:
On Apr 3, 2010, at 5:56 PM, Tim Cook wrote:
On Sat, Apr 3, 2010 at 7:50 PM, Tim Cook t...@cook.ms wrote:
Your experience is exactly why I suggested ZFS start doing some right
sizing if you will. Chop off a bit
On Apr 3, 2010, at 8:00 PM, Tim Cook wrote:
On Sat, Apr 3, 2010 at 9:52 PM, Richard Elling richard.ell...@gmail.com
wrote:
On Apr 3, 2010, at 5:56 PM, Tim Cook wrote:
On Sat, Apr 3, 2010 at 7:50 PM, Tim Cook t...@cook.ms wrote:
Your experience is exactly why I suggested ZFS start doing
: [zfs-discuss] To slice, or not to slice
Momentarily, I will begin scouring the omniscient interweb for information,
but I'd like to know a little bit of what people would say here. The
question is to slice, or not to slice, disks before using them in a zpool.
One reason to slice comes from
On 04/ 3/10 10:23 AM, Edward Ned Harvey wrote:
Momentarily, I will begin scouring the omniscient interweb for
information, but I’d like to know a little bit of what people would
say here. The question is to slice, or not to slice, disks before
using them in a zpool.
Not.
One reason to
On Fri, Apr 2, 2010 at 2:23 PM, Edward Ned Harvey
guacam...@nedharvey.comwrote:
There is some question about performance. Is there any additional
overhead caused by using a slice instead of the whole physical device?
zfs will disable the write cache when it's not working with whole disks,
On Fri, Apr 2, 2010 at 2:29 PM, Edward Ned Harvey solar...@nedharvey.comwrote:
I’ve also heard that the risk for unexpected failure of your pool is
higher if/when you reach 100% capacity. I’ve heard that you should always
create a small ZFS filesystem within a pool, and give it some reserved
On Apr 2, 2010, at 2:29 PM, Edward Ned Harvey wrote:
I’ve also heard that the risk for unexpected failure of your pool is higher
if/when you reach 100% capacity. I’ve heard that you should always create a
small ZFS filesystem within a pool, and give it some reserved space, along
with the
28 matches
Mail list logo
