Sponsored Content
Operating Systems Solaris How to create metadb when there is no free slice Post 302274417 by DukeNuke2 on Wednesday 7th of January 2009 02:03:52 PM
Old 01-07-2009
are all slices used or is simply no space left to asign it to a slice?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Add SWAP to free slice

I'm interested in adding more swap space to my current workstation (Solaris 10). I currently have 2 hard drives installed, however the system was only created with 512MB for swap that resides on drive 1. This drive is already sliced up and all slices are being used. The second drive has two... (3 Replies)
Discussion started by: here2learn
3 Replies

2. Solaris

mirroring the boot slice (slice 8) on x86

Hi there I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies

3. BSD

How to create IP table at Free BSD

Now, I had installed free bsd at my office. Unfortunitely, Email server have been using Local PoP3 and SMTP to our ISP with outlook. but my unix firewall sever ( free bsd ) didn't allow these port ( 110 & 25 ). How can i create the IP table to pass at server. If u have any experience about obvious... (4 Replies)
Discussion started by: Ashraff Ali
4 Replies

4. Linux

shrinking root partition and using free space to create a block device

We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies

5. Solaris

mirroring root disk using svm - but no free slices for metadb's

Hi all, we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this? In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies

6. Solaris

df –k shows 100% used for a slice even after min free has been decreased from 10% to

Hi Gurus, For a particular slice I have change the minfree from 10% to 1% with tunefs -m and its allowing the creation of file on that slice, however when I am seeing the same with df -k it says that the slice is 100% full. What could be reason for this? Thanks (2 Replies)
Discussion started by: kumarmani
2 Replies

7. Solaris

How to create metadb with zpool in Solaris 11

Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes? zpool status pool: rpool1 state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM rpool1 ONLINE 0 0 0 c4t1d0s0 ... (10 Replies)
Discussion started by: incredible
10 Replies

8. Solaris

Metadb

Hi, I have inherited a system with two disks mirrored, and only 1 metadb on each, I have deleted the db on c1t1 and recreated 3 which is fine. But when it comes to c1t0, the metadb -d /dev/dsk/c1t0d0s5 doesnt removed the existing db and the create metadb -a -f -c3 /dev/dsk/c1t0dos5 wont... (0 Replies)
Discussion started by: richard.tarlton
0 Replies

9. Solaris

Solaris 10 Volume Manager - adding slice to metadb

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

Trying to create ZFS slice on rpool

I have a 240GB disk as rpool. I have installed Solaris 11.3 to a partition which is 110GB. Now I have another 130GB which is unallocated. I want to use that additional space as a temporary folder to be shared between Solaris and Linux. The additional space had no /dev/dsk/c2t4... entry so I used... (8 Replies)
Discussion started by: kebabbert
8 Replies
DAR_XFORM(1)						      General Commands Manual						      DAR_XFORM(1)

NAME
dar_xform - disk archive "re-slicer" SYNOPSIS
dar_xform [options] [<path>/]source [<path>/]destination dar_xform -h dar_xform -V DESCRIPTION
dar_xform changes the size of slices of an existing archive. Source is the basename of the existing archive, destination is the basename of the archive to be created. If source basename is "-", the archive is read from standard input. If the destination basename is "-", the archive is written to standard output and -s option is not available. OPTIONS
-h displays help usage. -V displays version information. -b make the terminal ring when user interaction is required (like for example the creation of a new slice when using the -p option) -s <number> Size of the slices in bytes. If the number is followed by k (or K), M, G, T or P the size is in kilobytes, megabytes, gigabytes, terabytes or petabytes respectively. Example: by default "20M" means 20 megabytes it is the same as giving 20971520 as argument (see also -aSI and -abinary options). If -s is not present the backup will be written to a single slice whatever the size of the backup may be (there is probably some filesystem limitation, thus you might expect prob- lems with file size over 2 gigabytes, depending on your filesystem). -S <number> -S gives the size of the first slice which may be chosen independently of the size of following slices. This option needs -s and by default, the size of the first slice is the same as the one of the following slices. -p [<integer>] pauses before writing to a new slice (this requires -s). By default there is no pause, all slices are output in the same directory, up to the end of the backup or until the filesystem is full. In this later case, the user is informed of the lack of disk space and dar stops for user interaction. As soon as some disk space is available, the user can continue the backup. The optional integer that this option can receive tells dar to only pause very 'n' slice. Giving 3 for 'n' will make dar pause only after slices 3, 6, 9 and so on. If this integer is not specified, the behavior is as if '1' was given as argument which makes dar pause after each slice. -n Do not allow overwriting of any slice. -w Do not warn before overwriting slice. By default (no -n and no -w) overwriting is allowed but a warning is issued before proceeding. -E <string> the string is a command-line to be launched between the slices of the destination archive. See dar(1) man page (same option) for more information. -F <string> the string is a command-line to be launched between the slices of the source archive. See dar(1) man page (same option) for more information. -aSI[-unit[s]] when using k M G T E Z Y prefixes to define a size, use the SI meaning: multiple of 10^3 (a Mega is 1,000,000). -abinary[-unit[s]] when using k M G T E Z Y prefixes to define a size, use the historical computer science meaning: multiple of 2^10 (a Mega is 1,048,576). -aSI and -abinary can be used several times, they affect all prefix which follow even those found in file included by -B option up to the next -a... occurrence. Note that if in a file included by -B option an -abinary or -aSI is met, it affects all the following prefix even those outside the included files (for example in the following "-B some.dcf -s 1K" 1K may be equal to 1000 or 1024 depending on the pres- ence of an -aSI or -abinary in the file some.dcf. By default (before any -aSI/binary argument has been reached), binary interpretation of suffix is done (for compatibility with older versions). -Q Do not display any message on stderr when not launched from a terminal (for example when launched from an at job or crontab). Remains that any question to the user will be assumed a 'no' answer, which most of the time will abort the program. -j when virtual memory is exhausted, as user to make room before trying to continue. By default, when memory is exhausted dar aborts. -^ perm[:user[:group]] defines the permission and ownership to use for created slices. -3, --hash <algo> Beside each created slice is generated an on-fly hash file using the specified algorithm. Available algorithm are "md5" and "sha1", by default no hash file is generated. This option description is more detailed in dar man page (where it has the same designation as here). -; <src_num>[,<dst_num>] Defines the minimum number of digit to use for the source archive and for the destination archive. If you the source has not been defined with a minimum number of digit and you want to define a value for the destination archive, use zero (or one) as value for src. See the same option in dar man page for more details. NOTES
Dar_xform is not concerned by encryption or compression. It does not need to be aware of it to be able to change the slice scheme. Thus, it is not able to uncompress or uncipher an archive. EXIT CODES
dar_xform uses the same exit status as dar does, see dar(1) man page. SIGNALS
Any signal sent to dar_xform will abort the program immediately, there is no way to have a proper termination before the end of the process SEE ALSO
dar(1), dar_slave(1), dar_manager(1), dar_cp(1) KNOWN BUGS
None actually. AUTHOR
http://dar.linux.free.fr/ Denis Corbin France Europe 3rd Berkeley Distribution March 3rd, 2012 DAR_XFORM(1)
All times are GMT -4. The time now is 07:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy