07-20-2009
fssnap ioctl error
For some reason when I try to take a snapshot of the root slice on a particular machine I get an ioctl 22 error. I can't seem to find much on the problem by searching the internet other than some realtime processes such as ntp that use mlock can cause this to happen. I tried running it with truss and found nothing different other that the ioctl 22 when compared to the output of truss on a machine where I am able to take a snapshot. I even tried doing it from single user mode. The only thing I can think of is the root volume is a UFS filesystem managed by veritas volume manager. Any suggestions will be greatly appreciated.
10 More Discussions You Might Find Interesting
1. Programming
UNIX, gnu cc compiler, SUN Ultra 60
Hello, this is my first post, so please bear with me. I'm currently developing a test environment for a network subsystem that, when live, accesses databases and other network elements.
However, my test environment will be run offline, so I need to fake... (4 Replies)
Discussion started by: j_t_kim
4 Replies
2. Solaris
When I try to format a slice in Solaris 10 I get the follow error :
-bash-3.00# mkfs /dev/dsk/c1d0s5 18877824
Can not determine partition size: Inappropriate ioctl for device
Some format command output:....
AVAILABLE DISK SELECTIONS:
0. c1d0 <DEFAULT cyl 38735 alt 2 hd 64 sec 63>... (2 Replies)
Discussion started by: spoonman
2 Replies
3. Solaris
I managed to work with fssnap for snapshotting filesystems but, my question is..., is there a way we could get snapshots for the same point for multiple FS.
Wating on your help..., as i already did my trials what all i can!!
-ilan (0 Replies)
Discussion started by: ilan
0 Replies
4. Solaris
Hi Guys.
This is part of my filesystem structure :
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 47G 5.2G 42G 12% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% ... (2 Replies)
Discussion started by: aggadtech08
2 Replies
5. Solaris
Friends, I am learning the working of fssnap command.
Suppose there is a directory named /datadir which is of size 500mb.
I had taken the snapshot by means of the following command:
#fssnap -F ufs -o bs=/snapshotdir /datadir
{ it shows the o/p as
/dev/fssnap/0 }
My question is if... (2 Replies)
Discussion started by: saagar
2 Replies
6. Solaris
Hello All,
I am confused about the below outputs when I have tried fssnap output using diff path.
bash-3.00# /usr/lib/fs/ufs/fssnap -i ============>> o/p 1
Snapshot number : 0
Block Device : /dev/fssnap/0
Raw Device :... (0 Replies)
Discussion started by: vaibhav.kanchan
0 Replies
7. Shell Programming and Scripting
Hello to everyboyd i have a list of filesystem that i want to do a fssnap the idea is the bakcup
/
/var
/dbo
/Free
The logic is when i do a fssnap of / or /dbo or /Free the file that generetes the fssnap goes to /var but when i do a fssnap of /var goes to
/(and some folder). Can anybody... (0 Replies)
Discussion started by: enkei17
0 Replies
8. Solaris
Hi all!
Here's my situation:
I need to backup a running system before I can bring it down
I've tried performing a ufsdump while it's in multi-user mode but my ufsdump fails because there is too much activity on the system.
So I read that I could use fssnap to create a snapshot of (in my... (3 Replies)
Discussion started by: Keepcase
3 Replies
9. Red Hat
Hi!
I have a wondering regarding the syscalls automounter floods out when running strace on the process, are the below ioctl & futex messages bad? and is there any way to investigate em deeper?
ioctl(3, 0xffffffffc018937c, 0x417a8020) = -1 EAGAIN (Resource temporarily unavailable)
ioctl(3,... (5 Replies)
Discussion started by: Esaia
5 Replies
10. Solaris
Hi,
I have used Solaris but new to ZFS. I need to backup the root volume using fssnap.
zpool list
NAME SIZE ALLOC FREE CAP HEALTH ALTROOT
pool5 808G 552G 256G 68% ONLINE -
rpool 136G 20.9G 115G 15% ONLINE -
zfs list
NAME USED... (3 Replies)
Discussion started by: samnyc
3 Replies
LEARN ABOUT DEBIAN
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)