08-11-2018
Unfortunately I can't re-attach the device and force the import, because the device is long gone. It was a single-dev pool, too.
Last edited by priyadarshan; 08-11-2018 at 02:39 PM..
10 More Discussions You Might Find Interesting
1. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
2. Solaris
# zpool import
pool: emcpool1
id: 5596268873059055768
state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
devices and try again.
see: Sun Message ID: ZFS-8000-3C
config:
emcpool1 ... (7 Replies)
Discussion started by: fugitive
7 Replies
3. Solaris
Hello, I have a problem on my backup server. I lost my system hdd and my separate ZIL device while the system crashs and now I'm in trouble. The old system was running under the least version of osol/dev (snv_134) with zfs v22.
After the server crashs I was very optimistic of solving the problems... (2 Replies)
Discussion started by: ron2105
2 Replies
4. BSD
I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error:
# zpool create zfspool /dev/da0s1a
cannot create 'zfspool': no such pool or dataset
# zpool create zfspool /dev/da0
cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies
5. Solaris
Hi guys, I appreciate any help in this regard, we have lost sensitive data in the company.
One box with 2 disk mirrored and a 3ware controller handling 13 disks in a raidz2 pool. Suddenly the box restart and keeps "Reading ZFS config" for hours.
Unplugging disk by disk we isolate the disk... (3 Replies)
Discussion started by: tatxo
3 Replies
6. Solaris
Hi Guys,
I have a single ZFS pool with 2 disk which is mirrored if i create a new BE with lucreate should i specify which disk where the new BE should be created? (7 Replies)
Discussion started by: batas
7 Replies
7. Solaris
Hi,
Quick question.
I have a data zpool that consists of 1 disk.
pool: data
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
c0t50002AC0014B06BEd0 ONLINE... (2 Replies)
Discussion started by: general_lee
2 Replies
8. 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
9. Solaris
I have a single zpool with 3 2-way mirrors ( 3 x 2 way vdevs) it has a degraded disk in mirror-2, I know I can suffer a single drive failure, but looking at this how many drive failures can this suffer before it is no good? On the face of it, I thought that I could lose a further 2 drives in each... (4 Replies)
Discussion started by: fishface
4 Replies
10. Solaris
issue,
I had a zpool which was full
pool_temp1 199G 197G 1.56G 99% ONLINE -
pool_temp2 199G 196G 3.09G 98% ONLINE -
as you can see, full
so I replaced with a larger disk.
zpool replace pool_temp1 c3t600144F0FF8BA036000058CC1DB80008d0s0... (2 Replies)
Discussion started by: rrodgers
2 Replies
DEVCTL(4) BSD Kernel Interfaces Manual DEVCTL(4)
NAME
devctl -- device event reporting and device control interface
DESCRIPTION
The devctl device is used to report device events from the kernel. Future versions will allow for some device control as well.
IMPLEMENTATION NOTES
This design allows only one reader for /dev/devctl. This is not desirable in the long run, but will get a lot of hair out of this implemen-
tation. Maybe we should make this device a clonable device.
Also note: we specifically do not attach a device to the device_t tree to avoid potential chicken and egg problems. One could argue that all
of this belongs to the root node. One could also further argue that the sysctl(3) interface that we have now might more properly be an
ioctl(2) interface.
SIGIO support is included in the driver. However, the author is not sure that the SIGIO support is done correctly. It was copied from a
driver that had SIGIO support that likely has not been tested since FreeBSD 3.4 or FreeBSD 2.2.8!
The read channel for this device is used to report changes to userland in realtime. We return one record at a time. If you try to read this
device a character at a time, you will lose the rest of the data. Listening programs are expected to cope.
The sysctl and boot parameter hw.bus.devctl_disable is used to disable devctl when no devd(8) is running.
PROTOCOL
The devctl device uses an ASCII protocol. The driver returns one record at a time to its readers. Each record is terminated with a newline.
The first character of the record is the event type.
Type Description
! A notify event, such as a link state change.
+ Device node in tree attached.
- Device node in tree detached.
? Unknown device detected.
Message Formats
Except for the first character in the record, attach and detach messages have the same format.
Tdev at parent on location
Part Description
T + or -
dev The device name that was attached/detached.
parent The device name of the parent bus that attached the device.
location Bus specific location information.
The nomatch messages can be used to load devices driver. If you load a device driver, then one of two things can happen. If the device
driver attaches to something, you will get a device attached message. If it does not, then nothing will happen.
The attach and detach messages arrive after the event. This means one cannot use the attach message to load an alternate driver. The attach
message driver has already claimed this device. One cannot use the detach messages to flush data to the device. The device is already gone.
SEE ALSO
devd(8)
BSD February 11, 2003 BSD