I need to shrink a UFS slice with NetBSD on SPARC. seems the only way is backup+reformat. can someone please give me exact commands for that? presumably backup is file-by-file instead of sector-by-sector, but how to preserve permissions/dates/attributes.. ? thanks.
Hello,
I am using solaris 10 x86. my root and backup slices is having same memory 10 GB and same cylinders numbers . My root and backup cylinders ends at same cylinder number 1031. so for creating a new slice i am giving starting cylinder from 1302 and this is giving me error as "out of range" .... (2 Replies)
Hi Admins,
Server is sparc solaris 9
I am new into solaris with little experiemce with SVM.
/dev/dsk/c3t0d1s4 /u05
/dev/dsk/c3t0d1s3 /u02
/dev/dsk/c3t0d1s5 /u11
There are 3 file system created on slices of disk c3t0d1. Now i want to scrap all the slices and... (5 Replies)
Can anyone create a SPARC UFS Partition that is like 50 meg, DD the entire partition and zip it up and send it to me? Trying to play around with creating SPARC UFS partitions on linux and need a real one to compare to. I would do it but I do not have access to a SPARC machine anymore. I do not... (5 Replies)
Hi all
I'm having difficulty setting up a proper disk structure on a 72GB HDD. The drive was previously part of a zfs pool. The zpool has ben destroyed and now I want to use the disk in a raid 5 array. I need to partition the disk accordingly though.
This is what the partition table currently... (7 Replies)
Hi there,
I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server.
*I have re-compiled the linux kernel t support ufs fstype with ro mount support.
filesystem on solaris:... (3 Replies)
I downloaded the Solaris recommended patched for x86 and tried to install it, but I got the message that I dont have enough disk space. I don't want to install the patches without the option to back out. Anyway I did a df -k and found that my root mount point is in 948MB whereas my /export/home is... (5 Replies)
How do I create new disk slices taking space from an existing slice? Right now I have slice 6 (/usr) with 16G. I'd like to create slices 5 (/opt) and 7 (/export/home) and steal space from slice 6.
Thanks (3 Replies)
Anyone know if SUN recommends users to install the root parition on 1 single slice or break out the /var , /etc, /opt etc on separate slices?
What if i only have a single hdd that is only 2 GB (1 Reply)
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)