> Following suggestions from Andre and Rich that this was
> probably the ARC, I've implemented a 256Mb limit for my
> system's ARC, per the Solaris Internals wiki:
>
> * http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#ARCSIZE
> * set arc max to 256Mb
> set zfs:zfs_arc_max=0x1
1. Connect USB storage device (a disk) to machine
2. Find USB device through rmformat
3. Try zpool create on that device. It fails with:
can't open "/dev/rdsk/cNt0d0p0", device busy
If your disk was originally formatted with pcfs or ufs, it would be
automounted when connected. If you didn'
while playing around with ZFS and USB memory sticks or USB harddisks,
rmvolmgr tends to get in the way, which results in a
can't open "/dev/rdsk/cNt0d0p0", device busy
Do you remember exactly what command/operation resulted in this error? It is
something that tries to open device exclusive
Brilliant video, guys.
Totally agreed, great work.
Boy, would I like to see Peter Stormare in that video %)
-Artem.
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I thought that using a zfs import/export into it's own pool would work,
It works for me, at least on recent builds.
The only gotcha I'm aware of is that ZFS does not do well with I/O failures in a
non-replicated pool - it used to panic when there was read failure on a
single-disk USB pool,
# fstyp c3t0d0s0
zfs
s0? How is this disk labeled? From what I saw, when you put EFI label on a USB
disk, the "whole disk" device is going to be d0 (without slice). What do these
commands print:
# fstyp /dev/dsk/c3t0d0
# fdisk -W /dev/rdsk/c3t0d0
# fdisk -W /dev/rdsk/c3t0d0p0
-Artem.
_
I've updated the blog entry, no hacking around is necessary anymore. 'svcadm
disable volfs' is still recommended (vold/volfs will be completely removed
soon). USB is just an interface board slapped on the disk, there are disks with
both USB and SATA interfaces - you can connect with either cab
AMD Geodes are 32-bit only. I haven't heard any mention that they will
_ever_ be 64-bit. But, honestly, this and the Via chip aren't really
ever going to be targets for Solaris. That is, they simply aren't (any
substantial) part of the audience we're trying to reach with Solaris x86.
Didn'
I'm not sure if a unplug event generates FMA event, but it will generate
a unplug event ( I think it some different from a error ) which will be caught by tamarack
Tamarack is mostly for the desktop. Sure you can use it to do automatic 'zfs
import' on hotplug, but not for fault recovery. FMA
