| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: right way to report bugs |
| From: | Jan Derfinak <ja@xxxxxxxxxxxx> |
| Date: | Mon, 12 Dec 2005 23:26:57 +0100 (CET) |
| Cc: | Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx, overby@xxxxxxx |
| In-reply-to: | <20051213081217.C7432365@wobbly.melbourne.sgi.com> |
| References: | <Pine.LNX.4.61.0512121150540.11817@darkAngel.home.sk> <439DC63E.8030101@sgi.com> <20051213081217.C7432365@wobbly.melbourne.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Tue, 13 Dec 2005, Nathan Scott wrote: > > I think you've got it - file a bug, and harrass the list if no response :) > > In addition to that, a reproducible test case is invaluable > (in your case, an image of the corrupt filesystem; or even > better, a set of steps to get a filesystem into that failed > state - although that is rarely possible). Yes, I don't know how to get fs to this state, I just found it in this state when I tried to copy files. I know that it is not easy to fix bug without test case, so I prepared fs image and attached link on it, when I filled the bug. jan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS accessing arch-specific structures, Nathan Scott |
|---|---|
| Next by Date: | Re: right way to report bugs, Jan Derfinak |
| Previous by Thread: | Re: right way to report bugs, Nathan Scott |
| Next by Thread: | Re: right way to report bugs, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |