Re: [zfs-discuss] Drive upgrades

2012-04-17 Thread Peter Jeremy
On 2012-Apr-17 17:25:36 +1000, Jim Klimov wrote: >For the sake of archives, can you please post a common troubleshooting >techinque which users can try at home to see if their disks honour the >request or not? ;) I guess it would involve random-write bandwidths in >two cases? 1) Issue "disable wr

Re: [zfs-discuss] Drive upgrades

2012-04-17 Thread Richard Elling
On Apr 17, 2012, at 12:25 AM, Jim Klimov wrote: > 2012-04-17 5:15, Richard Elling wrote: >> For the archives... >> >> Write-back cache enablement is toxic for file systems that do not issue >> cache flush commands, such as Solaris' UFS. In the early days of ZFS, >> on Solaris 10 or before ZFS was

Re: [zfs-discuss] Drive upgrades

2012-04-17 Thread Jim Klimov
2012-04-17 5:15, Richard Elling wrote: For the archives... Write-back cache enablement is toxic for file systems that do not issue cache flush commands, such as Solaris' UFS. In the early days of ZFS, on Solaris 10 or before ZFS was bootable on OpenSolaris, it was not > uncommon to have ZFS and

Re: [zfs-discuss] Drive upgrades

2012-04-16 Thread Richard Elling
For the archives... On Apr 16, 2012, at 3:37 PM, Peter Jeremy wrote: > On 2012-Apr-14 02:30:54 +1000, Tim Cook wrote: >> You will however have an issue replacing them if one should fail. You need >> to have the same block count to replace a device, which is why I asked for a >> "right-sizing"

Re: [zfs-discuss] Drive upgrades

2012-04-16 Thread Edward Ned Harvey
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > boun...@opensolaris.org] On Behalf Of Peter Jeremy > > On 2012-Apr-14 02:30:54 +1000, Tim Cook wrote: > >You will however have an issue replacing them if one should fail. You need > to have the same block count to replace a devic

Re: [zfs-discuss] Drive upgrades

2012-04-16 Thread Peter Jeremy
On 2012-Apr-14 02:30:54 +1000, Tim Cook wrote: >You will however have an issue replacing them if one should fail. You need to >have the same block count to replace a device, which is why I asked for a >"right-sizing" years ago. The "traditional" approach this is to slice the disk yourself so y

Re: [zfs-discuss] Drive upgrades

2012-04-15 Thread Daniel Carosone
On Sat, Apr 14, 2012 at 09:04:45AM -0400, Edward Ned Harvey wrote: > Then, about 2 weeks later, the support rep emailed me to say they > implemented a new feature, which could autoresize +/- some small > percentage difference, like 1Mb difference or something like that. There are two elements to

Re: [zfs-discuss] Drive upgrades

2012-04-14 Thread Richard Elling
http://wesunsolve.net/bugid/id/6563887 -- richard On Apr 14, 2012, at 6:04 AM, Edward Ned Harvey wrote: >> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- >> boun...@opensolaris.org] On Behalf Of Freddie Cash >> >> I thought ZFSv20-something added a "if the blockcount is within 1

Re: [zfs-discuss] Drive upgrades

2012-04-14 Thread Edward Ned Harvey
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > boun...@opensolaris.org] On Behalf Of Freddie Cash > > I thought ZFSv20-something added a "if the blockcount is within 10%, > then allow the replace to succeed" feature, to work around this issue? About 2 yrs ago, I replaced a dri

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Stephan Budach
Am 13.04.12 19:22, schrieb Tim Cook: On Fri, Apr 13, 2012 at 11:46 AM, Freddie Cash > wrote: On Fri, Apr 13, 2012 at 9:30 AM, Tim Cook mailto:t...@cook.ms>> wrote: > You will however have an issue replacing them if one should fail. You need > to have

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Tim Cook
On Fri, Apr 13, 2012 at 11:46 AM, Freddie Cash wrote: > On Fri, Apr 13, 2012 at 9:30 AM, Tim Cook wrote: > > You will however have an issue replacing them if one should fail. You > need > > to have the same block count to replace a device, which is why I asked > for a > > "right-sizing" years a

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Michael Armstrong
Yes this Is another thing im weary of... I should have slightly under provisioned at the start or mixed manufacturers... Now i may have to replace 2tb fails with 2.5 for the sake of a block Sent from my iPhone On 13 Apr 2012, at 17:30, Tim Cook wrote: > > > On Fri, Apr 13, 2012 at 9:35 AM,

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Freddie Cash
On Fri, Apr 13, 2012 at 9:30 AM, Tim Cook wrote: > You will however have an issue replacing them if one should fail.  You need > to have the same block count to replace a device, which is why I asked for a > "right-sizing" years ago.  Deaf ears :/ I thought ZFSv20-something added a "if the blockc

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Tim Cook
On Fri, Apr 13, 2012 at 9:35 AM, Edward Ned Harvey < opensolarisisdeadlongliveopensola...@nedharvey.com> wrote: > > From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > > boun...@opensolaris.org] On Behalf Of Michael Armstrong > > > > Is there a way to quickly ascertain if my seagate/h

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Edward Ned Harvey
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > boun...@opensolaris.org] On Behalf Of Michael Armstrong > > Is there a way to quickly ascertain if my seagate/hitachi drives are as large as > the 2.0tb samsungs? I'd like to avoid the situation of replacing all drives and > then n

Re: [zfs-discuss] Drive upgrades

2012-04-13 Thread Volker A. Brandt
Michael Armstrong writes: > Is there a way to quickly ascertain if my seagate/hitachi drives are as > large as the 2.0tb samsungs? I'd like to avoid the situation of replacing > all drives and then not being able to grow the pool... Hitachi prints the block count of the drives on the physical pro

[zfs-discuss] Drive upgrades

2012-04-13 Thread Michael Armstrong
Hi Guys,I currently have a 18 drive system built from 13x 2.0tb Samsung's and 5x WD 1tb's... I'm about to swap out all of my 1tb drives with 2tb ones to grow the pool a bit... My question is...The replacement 2tb drives are from various manufacturers (seagate/hitachi/samsung) and I know from previo