| To: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS shutdown with 1.3.0 |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Wed, 3 Sep 2003 15:47:59 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <45181.213.173.165.140.1062566531.squirrel@xxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <41782.213.173.165.140.1062330069.squirrel@xxxxxxxxxxxxxxxxxxxxxxx> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@xxxxxxxxxxxxxxxxxxxxxxx> <45181.213.173.165.140.1062566531.squirrel@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Wed, Sep 03, 2003 at 07:22:11AM +0200, Simon Matter wrote: > Nathan, > > I have now run xfs_repair without -n several times but it still segfaults > in the same place. Although the filesystem is still mountable, I'm a bit > worried... > How do I call xfs_repair with gdb to produce useful output? Do I need a > debug enabled version of xfs_repair? IIRC, by default we build the tools with -g, so symbols should be visible to gdb as is. Here's the command line you're after: # gdb -q /bin/xfs_repair (gdb) r /dev/XXX ... (gdb) where ... etc ... cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS shutdown with 1.3.0, Simon Matter |
|---|---|
| Next by Date: | how stable is XFS kernel 2.4.22, How Wong |
| Previous by Thread: | Re: XFS shutdown with 1.3.0, Simon Matter |
| Next by Thread: | Re: XFS shutdown with 1.3.0, Simon Matter |
| Indexes: | [Date] [Thread] [Top] [All Lists] |