12-28-2006
You have a problem there, your root filesystem is full and since its a production server that needs to be up 24/7 you better clean it up.
Look in /var/adm for old log files that you might be able to remove. Check for any core dumps in /var/crash aswell. syslogs can also get big.
If you want to flare the root partition you can not use /tmp as it is only 7GB and you root partition is 10GB.
Use absdata5 or absdata6 as you have 51GB available there.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have a solaris 5.6 box, and i need to create a Flash Archive for DRP porposes. When i execute the falarcreate commnad the system returns "flarcreate: command not found" . I search the entire system (find . -name *flar*) for that comand and i can find it. Solaris 5.6 donīt have this... (1 Reply)
Discussion started by: spacewalker
1 Replies
2. Solaris
Hi,
Someone knows hot to create a flash archive to a remote tape device?
Here is my try:
$flarcreate -n nereus -S -t lisdev:/dev/rmt/1n
WARNING: hash generation disabled when using tape (-t)
current filter settings
Creating the archive...
ERROR: Unable to work archive.
Regards (4 Replies)
Discussion started by: spacewalker
4 Replies
3. Solaris
Hi there
I have created a flash archive using flarcreate and rolled out via jumpstart and everything seems fine, however when I roll out the archive to another box, everything is fine apart from the /etc/hosts file which is the same as the masters hosts file (i.e. it still has the original... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
4. Solaris
found my notes got it
flarcreate -n jumpstart -x /jumpstart/flash /jumpstart/flash/jumpstart.flar
i think this will omit that directory and save it there correct? (3 Replies)
Discussion started by: deaconf19
3 Replies
5. Solaris
Hi, i'm trying to make a system copy from one server to another (solaris 9), they have the same configuration. I've tried to create a flash archive using the flarcreate but the flash file size is 5.06 approx. and the method the flarcreate is using is CPIO and he cannot handle sizes over 4 GB.
Is... (2 Replies)
Discussion started by: pasalagua
2 Replies
6. Solaris
I am trying to take Solaris OS backup with the following command
"flarcreate -S -n / /server11/inblr.flar", but this is taking complete root / (which includes my othe mount points also),
Can any one suggest how to take only solaris OS backup and restore proceedure
Thanks in advance (4 Replies)
Discussion started by: raj.chinnu
4 Replies
7. Solaris
Hi, I have to clone a system and i would like to use flarcreate. My question is regarding excluding some NFS mounts and some directories under /. If somebody have done this earlier please advice on the following procedure.
Create a file like /exclude_list and put the following lines in it
... (1 Reply)
Discussion started by: uxadmin007
1 Replies
8. Solaris
Hello Forum,
I'd like to clone a Solaris 10 System. Well, I read a lot about flarcreate.
Anyway I only read how to _create a flash archive by using flarcreate. But I don't know how to copy the data back to another harddisk from an ar:confused:chive to get a second runing system.
... (4 Replies)
Discussion started by: borsti007
4 Replies
9. Solaris
hi,
i would like to know if it is posible to create the flash archive and in the same line add another command to save it in another server through SCP.
flarcreate -n "sv756flash" -c -X excludefilelist |...
i appreciate your help.
thanks a lot. (4 Replies)
Discussion started by: pabloli150
4 Replies
10. Solaris
Got a solaris 10 server that I want to take a flar of in order to use to build a new server. Works fine.
Only trouble is there is software on the original server that is not needed on the new server - it will be uninstalled.
I was thinking of creating the flar from the original server and... (0 Replies)
Discussion started by: psychocandy
0 Replies
LEARN ABOUT XFREE86
voldump
VOLDUMP(8) AFS Command Reference VOLDUMP(8)
NAME
voldump - Dump an AFS volume without using the Volume Server
SYNOPSIS
voldump -part <partition> -volumeid <volume id>
[-file <dump file>] [-verbose] [-help]
voldump -p <partition> -vo <volume id>
[-f <dump file>] [-ve] [-h]
DESCRIPTION
voldump dumps an AFS volume in the format used by vos dump without using the Volume Server. It must be run on the file server machine and
usually must be run as the superuser "root" to have permissions to read the file server data. It's primary use is to recover data from a
file server machine where the Volume Server cannot be started for some reason.
The dump output will go to standard output, or to a file if -file is specified. vos restore can be used to load the resulting dump into a
new AFS volume. voldump always does a full dump.
CAUTIONS
Normally, use vos dump instead of this command. voldump is a tool of last resort to try to extract data from the raw data structures
stored on the file server machine and is not as regularly tested or used as the normal vos dump implementation.
If the AFS volume being dumped changes while voldump is running, the results may be inconsistent. If the File Server and Volume Server are
running, stop them with bos shutdown or a similar method before running this command.
OPTIONS
-part <partition>
Names the partition on which the volume to be dumped is located. voldump does not take the normal full range of ways of specifying a
partition. Instead, partition must be either a single letter between "a" and "z", corresponding to /vicepa through /vicepz, or the
full path to the file server partition. "aa" is not recognized; use /vicepaa instead.
-volumeid <volume id>
Specifies the ID of the volume to dump. The volume must be specified by numeric ID, not by name.
-file <dump file>
Specifies the output file for the dump. If this option is not given, the volume will be dumped to standard output.
-verbose
Asks for a verbose trace of the dump process. This trace information will be sent to standard error.
EXAMPLES
The following command dumps the volume 1936964939 on the /vicepb partition to the file /tmp/volume.dump:
% voldump -part /vicepb -volumeid 1936964939 -file /tmp/volume.dump
PRIVILEGE REQUIRED
The issuer must have read access to the file server data stored in the specified partition. Usually, this means that the issuer must be
the local superuser "root" on the file server machine.
SEE ALSO
bos_shutdown(8), restorevol(1), volserver(8), vos_dump(1), vos_restore(1)
COPYRIGHT
Copyright 2005 Russ Allbery <rra@stanford.edu>
This documentation is covered by the IBM Public License Version 1.0. This man page was written by Russ Allbery for OpenAFS.
OpenAFS 2012-03-26 VOLDUMP(8)