09-08-2011
Yeah, there isn't much point in setting up your meta database on your ZFS disks. You should have your meta database on the disks that you're actually using for LVM.
10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
If solaris has metadb services on the disk, it means that it has a HW raid controller. Or what.
Thanks in advance. (1 Reply)
Discussion started by: itik
1 Replies
2. Solaris
Hi All,
I have to do disk mirroring, for that I have to create a metadb as disk mirroring have to do with SVM. However I do not have any slice free for metadb.
What are the options? Please suggest (4 Replies)
Discussion started by: kumarmani
4 Replies
3. Solaris
Hello,
I have a 520GB SAN resource connected to the server via FC (4Gbit).
In the next step he wants to create pool storage:
After 15 hours Pool has not yet created...
Is such a long waiting time is normal? Should I have done?
Regards (1 Reply)
Discussion started by: bieszczaders
1 Replies
4. Solaris
I have a solaris zone of 12 GB and i have to increase the / filesystem to 31GB as requested. Earlier I had expanded filesystems other than / by setting quota to new value like "zfs set quota=new value mountpoint" but I am not sure whether its a good practice in zfs because by default in my... (5 Replies)
Discussion started by: vikkash
5 Replies
5. 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
6. Solaris
Check Solaris VM Databases metadb does not have enough information about logical volumes. Current value is 0%
I have checked the SVM status, all disks are good state and synched perfectly. no errors in metadb -i.
what is this alert exact mean? what we have to check for the value?
Please... (1 Reply)
Discussion started by: Naveen.6025
1 Replies
7. Solaris
Hi everyone,
I'm hoping someone can help me out here. I've googled lots and don't think I can find an easy answer to this.
We're in the process of upgrading Solaris from v10 5/08 to v10 9/10. The zpools for luns are currently at version 10, and I understand Solaris v10 9/10 has support for... (3 Replies)
Discussion started by: badoshi
3 Replies
8. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
9. Solaris
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
10. Solaris
how to recovery metadb?
Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
LEARN ABOUT REDHAT
vgscan
VGSCAN(8) System Manager's Manual VGSCAN(8)
NAME
vgscan - scan all disks for volume groups and build /etc/lvmtab and /etc/lvmtab.d/* which are the database for all other lvm commands.
SYNOPSIS
vgscan [-d|--debug] [-f|--forcenumbers] [-h|--help] [-r|--remove_snapshots [VolumeGroupName]] [-v|--verbose]
DESCRIPTION
vgscan scans all SCSI, (E)IDE disks, multiple devices and a bunch of other disk devives in the system for volume groups defined.
OPTIONS
-d, --debug
Enables additional debugging output (if compiled with DEBUG).
-f, --forcenumbers
If used volume group and/or logical volume minor numbers are found during scan, replace them. This will potentially cause problems
for NFS exported filesystems on logical volumes with changed numbers.
-h, --help
Print a usage message on standard output and exit successfully.
-r, --remove_snapshots [VolumeGroupName]
Remove all snapshot logical volumes from all or just the named volume group.
-v, --verbose
Display verbose information of vgscan's activities.
Hint
Put vgscan in one of your system startup scripts. This gives you an actual logical volume manager database before activating all volume
groups by doing a "vgchange -ay".
DIAGNOSTICS
vgscan returns an exit code of 0 for success and > 0 for error:
1 error reading physical volumes
2 error inserting vokume group name into lvmtab
3 no volume group(s) found
4 error creating lvmtab
5 no or not enough free device specials to store volume group in lvmtab
6 error storing VGDA on disk(s)
7 reused LV device number
8 error releasing snapshot logical volume
95 driver/module not in kernel
96 invalid I/O protocol version
97 error locking logical volume manager
99 invalid command line
See also
lvm(8), vgcreate(8), vgchange(8)
AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGSCAN(8)