This is for the archive, as well as anyone who cares, but I recently ran into an interesting XFS bug. xfs_db -r /dev/root xfs_db: sb 1 xfs_db: print uuid uuid = 9d44dc2e-9363-1024-8e23-080069124456 xfs_db: What you see above is a normal filesystem output. What I was seeing was amanda reporting xfsdump exiting on signal 1 for that filesystem. A support call to SGI and they pointed out my problem. There's a bug that SGI hasn't managed to reliably reproduce (and thusly squash) which causes uuid to be set to null on very rare occasion (this is the first time I've seen it in 5+ years dealing with XFS). You can run xfsdump with the -J flag and dump the filesystem, but the only real fix is the dump the filesystem, mkfs it, and restore the data. Running xfsdump on the command line returned no value at all that was reported. It just exited to the command line after it estimated the dumpsize for the filesystem in question. Using -J worked fine. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen <[EMAIL PROTECTED]>
