Does the suspend event only occur on SMB clients or does it impact the
other storage clients when triggered by the Windows clients?
Any domain controller event errors?
dmsg output?
fmdump -eV output?
uname -a output?
Have you attempted a packet capture of the event?
snoop -o smb-client.cap
--
I had similar issues before I enabled TLER, and disabled the head parking
on my WD Green drives. A quick Google shows some evidence of similar
features on the 3TB Hitachis.
On Tue, Jun 12, 2012 at 9:55 PM, Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Tue, 12 Jun 2012, John McEntee
On Tue, 12 Jun 2012, John McEntee wrote:
I am having problems with a openindiana storage server I have built am I am
trying to track down the cause to fix it. The current symptoms are seen from
all windows clients (both 7 and XP) that will report an error stating.
Path File is not accessible. T
That is absolutely stunning.
Many thanks for that. I guess I'm going to have to bite the bullet, wait
until I've got another two 3tb drives and create a new pool.
Thanks to all for the feedback. Your patience with me is much appreciated.
On 12/06/12 17:44, Jim Klimov wrote:
2012-06-12 19:22,
2012-06-12 19:22, Jim Klimov wrote:
First of all, I believe this snippet belongs on a Wiki page,
and I'll try to make one to sum up all knowledge and FUD we
have about The AShift Problem ;) At least, it would be easier
to point people to this page as a common answer ;)
FWIW, here is the first d
2012-06-12 19:00, Bob Friesenhahn wrote:
On Tue, 12 Jun 2012, George Wilson wrote:
Illumos has a way to override the physical block size of a given disk
by using the sd.conf file. Here's an example:
sd-config-list =
"DGC RAID", "physical-block-size:4096",
"NETAPP LUN", "physical-b
Actually I found the following blog quite illuminating.
http://www.big-bubbles.fluff.org/blogs/bubbles/blog/2012/02/04/placeholder-migrating-a-zfs-root-pool/
It would have to be worked thru for a number of specific cases. But it
is basically sound.
A bird's eye view might be: format the new
On Jun 12, 2012, at 11:00 AM, Bob Friesenhahn wrote:
> On Tue, 12 Jun 2012, George Wilson wrote:
>>
>> Illumos has a way to override the physical block size of a given disk by
>> using the sd.conf file. Here's an example:
>>
>> sd-config-list =
>> "DGC RAID", "physical-block-size:4096
On Tue, 12 Jun 2012, George Wilson wrote:
Illumos has a way to override the physical block size of a given disk by using
the sd.conf file. Here's an example:
sd-config-list =
"DGC RAID", "physical-block-size:4096",
"NETAPP LUN", "physical-block-size:4096";
By adding the
On Jun 12, 2012, at 12:58 AM, Rich wrote:
> On Tue, Jun 12, 2012 at 12:50 AM, Richard Elling
> wrote:
>> On Jun 11, 2012, at 6:08 PM, Bob Friesenhahn wrote:
>>
>>> On Mon, 11 Jun 2012, Jim Klimov wrote:
ashift=12 (2^12 = 4096). For disks which do not lie, it
works properly out of the
Yes it will. The only way to do this is to create a secondary pool and
send/receive your root pool to the new pool.
- George
On Jun 11, 2012, at 7:16 PM, Rich wrote:
> Won't zpool replace fail b/c the new disks require ashift=12 and his
> existing pool devices have ashift=9?
>
> - Rich
>
> On
I am having problems with a openindiana storage server I have built am I am
trying to track down the cause to fix it. The current symptoms are seen from
all windows clients (both 7 and XP) that will report an error stating.
Path File is not accessible. The specified network name is no longer
a
On 6/12/12 9:32 AM, Jim Klimov wrote:
2012-06-12 16:45, Gary Gendel wrote:
On 6/12/12 8:00 AM, Jim Klimov wrote:
Did the 3TB disk also report to the OS that it uses 4k sectors?
What ashift value is used by the pool, ultimately? Example:
# zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
ashift:
Jim Klimov wrote:
> As for the striped pool size - it seems about right.
> My 3TB disk is 2.72T, so a 4TB set being 3.6T seems okay.
> The raid10 mix also can have mixed ashifts, i.e. using ashift=12
> for the 3TB disks and ashift=9 for 1TB disks, if that's configured.
Don't forget that disk manuf
2012-06-12 17:32, Jim Klimov wrote:
I have these striped with a 1TB mirrored drive
Is your 1TB disk mirrored? Otherwise its single failure can bring
the whole pool down.
Scratch that question, my bad ;)
//Jim
___
OpenIndiana-discuss mailing list
Op
2012-06-12 16:45, Gary Gendel wrote:
On 6/12/12 8:00 AM, Jim Klimov wrote:
Did the 3TB disk also report to the OS that it uses 4k sectors?
What ashift value is used by the pool, ultimately? Example:
# zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
ashift: 9
ashift: 9
ashift: 9
I did check the ashift after the upgrade and both 3TB HDs report ashift=12.
I am actually using an HP N35L (1.3 Ghz vs. 1.5 GHz in the N40L) and I have
8 GB of non-ECC DDR3 so I could not answer the memory question.
These little machines are really great (If they came with SATA 3, they
would be t
On Jun 11, 2012, at 9:58 PM, Rich wrote:
> On Tue, Jun 12, 2012 at 12:50 AM, Richard Elling
> wrote:
>> On Jun 11, 2012, at 6:08 PM, Bob Friesenhahn wrote:
>>
>>> On Mon, 11 Jun 2012, Jim Klimov wrote:
ashift=12 (2^12 = 4096). For disks which do not lie, it
works properly out of the bo
On 6/12/12 8:00 AM, Jim Klimov wrote:
Did the 3TB disk also report to the OS that it uses 4k sectors?
What ashift value is used by the pool, ultimately? Example:
# zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
ashift: 9
ashift: 9
ashift: 9
ashift: 9
If your 4KB disks u
2012-06-12 11:24, michelle wrote:
Is there a way for the system to me a bit more clever; we have 4k
sectors now but how long before that is upped again; maybe another decade?
After all, if it is a redundant set, what is the reason why it can't
just dump the disk to be replaced and rebuild on the
2012-06-12 15:40, J. V. пишет:
On 12/06/12 09:16 AM, Rich wrote:
Won't zpool replace fail b/c the new disks require ashift=12 and his
existing pool devices have ashift=9?
This should work fine:
HP Microserver, upgrading a mirrored pool from 2TB HDs to 3TB HDs. At one
point, the pool had one 2
On 12/06/12 09:16 AM, Rich wrote:
> Won't zpool replace fail b/c the new disks require ashift=12 and his
> existing pool devices have ashift=9?
This should work fine:
HP Microserver, upgrading a mirrored pool from 2TB HDs to 3TB HDs. At one
point, the pool had one 2TB HD with 512 sectors and the
Is there a way for the system to me a bit more clever; we have 4k
sectors now but how long before that is upped again; maybe another decade?
After all, if it is a redundant set, what is the reason why it can't
just dump the disk to be replaced and rebuild on the new drive?
I know I'm being a
We know, from people like Michelle on HDD problems, recently, that just
adding an ashift=12 disk to a pool with ashift=9 won't work.
On 2012-06-12 01:55, James C. McPherson wrote:
On 12/06/12 09:16 AM, Rich wrote:
Won't zpool replace fail b/c the new disks require ashift=12 and his
existing
24 matches
Mail list logo
