On 3/1/13 3:37 AM, Ole Tange wrote: > On Thu, Feb 28, 2013 at 7:48 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: >> On 2/28/13 9:22 AM, Ole Tange wrote: > >>> /usr/local/src/xfsprogs-3.1.10/repair# ./xfs_repair -n /dev/md5p1 > [...] >>> Segmentation fault (core dumped) >>> >>> Core put in: http://dna.ku.dk/~tange/tmp/xfs_repair.core.bz2 >> >> We'd need a binary w/ debug symbols to go along with it. > > http://dna.ku.dk/~tange/tmp/xfs_repair > >> an xfs_metadump might recreate the problem too. > > # sudo ./xfs_metadump.sh -g /dev/md5p1 - | pbzip2 > > /home/tange/public_html/tmp/metadump.bz2 > xfs_metadump: cannot init perag data (117) > Copying log I'll take a look. May be that the error renders it invalid but we'll see. > http://dna.ku.dk/~tange/tmp/metadump.bz2 > > Please consider providing an example in the man page for xfs_metadump e.g: > > xfs_metadump.sh -g /dev/sda2 meta.dump >From the manpage, SYNOPSIS xfs_metadump [ -efgow ] [ -l logdev ] source target The source argument must be the pathname of the device or file containing the XFS filesystem and the target argument specifies the destination file name. is not enough? Thanks, -Eric > > /Ole > > _______________________________________________ > xfs mailing list > xfs@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs > _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
