On 6/17/19 7:09 AM, grin wrote: > Hello, > > I haven't checked XFS project lately, and that's a decade or so, it > means that when I have met a bug I went out and tried to see where and > how to report. Just mentioning the following, since you may not be > aware from the inside: > > The xfs.org seems to be the "main" xfs website, search gives it first, > and has a huge amount of informations. Problem is: most links point to > nonexistant pages (SGI links hijacked by HP main page), including those > mentioning documentation, development or suggest bug reporting. Only > two valid pointers are the #xfs on FreeNode and this mailing list. Some > mentioned https://xfs.wiki.kernel.org/ which is bacially impossible to > find unless looking for it specifically, and it doesn't contain much > info anyway. So I can't see who to mention this to, maybe you know. yes sadly no xfs devs own xfs.org > Anyway. xfs_db SIGSEGV, v5.0, pretty reliably, on >> inode <n> >> type inode >> print > [...lots of output of the extents...] > crash > > I am not sure how it's handled: whether it's a very low level utility > and sigsegv is a way to show "you're doing something wrong", or rather > it is a bug and shall be fixed. If you would kindly tell me whether > I shall report it anywhere, send metadump, or anything, I would be much > happier (to know at least). > > (At least one external tool tries to use it and it's bitten by the > crash.) core + binary perhaps? Or provide a gdb backtrace, or a metadump of the filesystem? If you want to provide a metadump I'd suggest contacting me off list to do so. Thanks, -Eric > Thanks, > g >
