Package: xfsdump Version: 2.2.27-1 Severity: important Running current Debian Sarge code with the i686 kernel. xfsdump reports that any directory I specify to back up does not identify a file system. A zero (0) length bbackup output file is created "/ext_backup/cirlnx01/pdoxdata" by the program before it exits.
Google turned up this link that this is not an isolated case. http://www.ussg.iu.edu/hypermail/linux/kernel/0502.2/1482.html Per that message, I have attached the -v 5 output below. cirlnx01:/# xfsdump -e -F -f /ext_backup/cirlnx01/pdoxdata -L $STAMP"PDoxData" -l 0 -v 5 /srv/shares/pdoxdata/ xfsdump: RLIMIT_AS org cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_STACK org cur 0x800000 max 0xffffffffffffffff xfsdump: raising stack size soft limit from 0x800000 to 0x2000000 xfsdump: RLIMIT_STACK new cur 0x2000000 max 0xffffffffffffffff xfsdump: RLIMIT_DATA org cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_FSIZE org cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_FSIZE now cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_CPU cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_CPU now cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: INTGENMAX == 2147483647 (0x7fffffff) xfsdump: UINTGENMAX == 4294967295 (0xffffffff) xfsdump: OFF64MAX == 9223372036854775807 (0x7fffffffffffffff) xfsdump: OFFMAX == -1 (0x7fffffff) xfsdump: SIZEMAX == 4294967295 (0xffffffff) xfsdump: INOMAX == 4294967295 (0xffffffff) xfsdump: TIMEMAX == 2147483647 (0x7fffffff) xfsdump: SIZE64MAX == 18446744073709551615 (0xffffffffffffffff) xfsdump: INO64MAX == 18446744073709551615 (0xffffffffffffffff) xfsdump: UINT64MAX == 18446744073709551615 (0xffffffffffffffff) xfsdump: INT64MAX == 9223372036854775807 (0x7fffffffffffffff) xfsdump: UINT32MAX == 4294967295 (0xffffffff) xfsdump: INT32MAX == 2147483647 (0x7fffffff) xfsdump: INT16MAX == 32767 (0x7fff) xfsdump: UINT16MAX == 65535 (0xffff) xfsdump: getpagesize( ) returns 4096 xfsdump: parent pid is 9857 xfsdump: effective user id is 0 xfsdump: using file dump (drive_simple) strategy xfsdump: version 2.2.27 (dump format 3.0) - Running single-threaded xfsdump: ERROR: /srv/shares/pdoxdata/ does not identify a file system xfsdump: usage: xfsdump [ -a (dump DMF dualstate files as offline) ] [ -b <blocksize> ] [ -c <media change alert program> ] [ -d <dump media file size> ] [ -e (allow files to be excluded) ] [ -f <destination> ... ] [ -h (help) ] [ -l <level> ] [ -m (force usage of minimal rmt) ] [ -o (overwrite tape) ] [ -p <seconds between progress reports> ] [ -q <use QIC tape settings> ] [ -s <subtree> ... ] [ -v <verbosity {silent, verbose, trace}> ] [ -z <maximum file size> ] [ -A (don't dump extended file attributes) ] [ -B <base dump session id> ] [ -E (pre-erase media) ] [ -F (don't prompt) ] [ -I (display dump inventory) ] [ -J (inhibit inventory update) ] [ -L <session label> ] [ -M <media label> ... ] [ -O <options file> ] [ -R (resume) ] [ -T (don't timeout dialogs) ] [ -Y <I/O buffer ring length> ] [ - (stdout) ] [ <source (mntpnt|device)> ] xfsdump: main.c: 1113: mlog_exit called: exit_code: ERROR return: OPT_ERROR (bad command line option) xfsdump: main.c: 597: mlog_exit called: exit_code: ERROR return: INIT_ERROR (could not initialise subsystem) xfsdump: Dump Status: ERROR Indeed it does identify a file system, output below... cirlnx01:/# ls -al /srv/shares/pdoxdata/ total 4 drwxrwxrwx 4 root root 30 2005-04-21 04:55 . drwxr-xr-x 7 root root 70 2005-04-17 03:57 .. drwxrwxrwx 2 mdlueck mdlueck 25 2005-04-21 04:56 Locks drwxrwxrwx 2 mdlueck mdlueck 4096 2005-04-21 04:56 Style Please advise if there is anything I can do of assistance in resolving this issue. Thanks! Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]