01-14-2011
I have the same problem. I accidentally overwrote the drive with ZIL when upgrading from OpenSolaris 2009.11, to Solaris 11 Express (151a). Now I can't import the pool, even with the -m option (which documentation explicitly says it to do just that).
Sorry I don't have an answer for you (yet), but your effort - and more specifically your post - has at least save ME from potentially weeks of hair-pulling similar to what you have done.
I love the IDEA of ZFS, but in truth I have seen a significant "negative" benefit over the years of using it. I.E., loss of data. Solaris is so damn fickle and exceptionally fragile (as an operating system...and as I'm learning, ZFS is too). I mean, come on! The whole idea of an separate ZIL was to improve performance...and hopefully not at the expense of reliability! From now on, I will be disabling the ZIL altogether. (And the moment btrfs is production-ready on Linux, will migrate everything to that in a heartbeat.)
Who would have thought that losing the ZIL would render all of your data useless!?? Talk about unnecessary additional points of failure. (Even if mirrored...still an additional point of failure.) This risk, IMO, vastly outweighs the risk of asynchronous IO, unless you are running something that explicitly (i.e. documented) requires synchronous IO such as apps/databases that life and/or lots of $ depends on.
Anyway. I'm going to try to import via Linuz/ZFS-FUSE. If that fails I'll have to try to reconstruct the data via sporadic offline backups. I'll keep ya posted.
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi all,
I am looking at a MC cluster comprised of 2 nodes. There is a package named backup which does nothing more than mount a VG.
At one point we noticed errors in syslog that look like this:
cmclconfd: Could not access device file /dev/dsk/c20t0d0: No such file or directory
There are... (1 Reply)
Discussion started by: mariusp
1 Replies
2. Solaris
Hi,
I need to create 4 zones.
I have an array with a RAID5 volume. I have exported 4 LUNS from the array. Now my host see the 4 LUNS as raw devices.
I am partitioning each LUN using format then mounting each slice on the global zone. Then I am using each slice as a file system for my non... (3 Replies)
Discussion started by: general_lee
3 Replies
3. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
4. HP-UX
Hello,
I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name:
ioscan -C disk -f -n -k | more
A typical... (5 Replies)
Discussion started by: bstring
5 Replies
5. Solaris
Weird duplicate device in one of my nested raidz1s - device is shown as both online and unavailable, with a hot spare showing up as degraded as well.
Any thoughts on how I should proceed?
root@storage# zpool status tank
pool: tank
state: DEGRADED
status: One or more devices are... (6 Replies)
Discussion started by: DoohanMcGirk
6 Replies
6. Solaris
A backup/clone script of ours was recently ran. It normally only clones the rpool and renames in rpoolA. Something must've changed as it found another one of our pools that it shouldn't have. It exported that pool unbeknownst to us. Later on when a coworker realized the other pool was missing he... (2 Replies)
Discussion started by: beantownmp
2 Replies
7. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
8. Solaris
On an OmniOS server, I removed a single-disk pool I was using for testing.
Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore.
# zpool import
pool: fido
id: 7452075738474086658
state: FAULTED
status: The pool was last... (11 Replies)
Discussion started by: priyadarshan
11 Replies
LEARN ABOUT SUNOS
device_allocate
device_allocate(4) File Formats device_allocate(4)
NAME
device_allocate - device_allocate file
SYNOPSIS
/etc/security/device_allocate
DESCRIPTION
The device_allocate file contains mandatory access control information about each physical device. Each device is represented by a one line
entry of the form:
device-name;device-type;reserved;reserved;auths;device-exec
where
device-name This is an arbitrary ASCII string naming the physical device. This field contains no embedded white space or non-
printable characters.
device-type This is an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices
of like type. This field contains no embedded white space or non-printable characters.
reserved This field is reserved for future use.
reserved This field is reserved for future use.
auths This field contains a comma-separated list of authorizations required to allocate the device, or asterisk (*) to
indicate that the device is not allocatable, or an '@' symbol to indicate that no explicit authorization is needed
to allocate the device.
The default authorization is solaris.device.allocate. See auths(1)
device-exec This is the physical device's data purge program to be run any time the device is acted on by allocate(1). This is
to ensure that all usable data is purged from the physical device before it is reused. This field contains the
filename of a program in /etc/security/lib or the full pathname of a cleanup script provided by the system adminis-
trator.
The device_allocate file is an ASCII file that resides in the /etc/security directory.
Lines in device_allocate can end with a `' to continue an entry on the next line.
Comments may also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'.
White space is allowed in any field.
The device_allocate file must be created by the system administrator before device allocation is enabled.
The device_allocate file is owned by root, with a group of sys, and a mode of 0644.
EXAMPLES
Example 1: Declaring an allocatable device
Declare that physical device st0 is a type st. st is allocatable, and the script used to clean the device after running deallocate(1) is
named /etc/security/lib/st_clean.
# scsi tape
st0;
st;
reserved;
reserved;
solaris.device.allocate;
/etc/security/lib/st_clean
Example 2: Declaring an allocatable device with authorizations
Declare that physical device fd0 is of type fd. fd is allocatable by users with the solaris.device.allocate authorization, and the script
used to clean the device after running deallocate(1) is named /etc/security/lib/fd_clean.
# floppy drive
fd0;
fd;
reserved;
reserved;
solaris.device.allocate;
/etc/security/lib/fd_clean
Notice that making a device allocatable means that you need to allocate and deallocate it to use it (with allocate(1) and deallocate(1)).
If a device is not allocatable, there will be an asterisk (*) in the auths field, and no one can use the device.
FILES
/etc/security/device_allocate Contains list of allocatable devices
SEE ALSO
auths(1), allocate(1), bsmconv(1M), deallocate(1), list_devices(1), auth_attr(4)
NOTES
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for
more information.
SunOS 5.10 17 Mar 2003 device_allocate(4)