| To: | Jan Derfinak <ja@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: right way to report bugs |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Tue, 13 Dec 2005 11:40:18 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.61.0512122251370.14984@darkAngel.home.sk> |
| References: | <Pine.LNX.4.61.0512121150540.11817@darkAngel.home.sk> <439DC63E.8030101@sgi.com> <20051213081217.C7432365@wobbly.melbourne.sgi.com> <Pine.LNX.4.61.0512122251370.14984@darkAngel.home.sk> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Mon, Dec 12, 2005 at 11:26:57PM +0100, Jan Derfinak wrote: > 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. Sorry, I overlooked that - thanks Jan. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: right way to report bugs, Jan Derfinak |
|---|---|
| Next by Date: | Re: deep chmod|chown -R begin to start OOMkiller, David Chinner |
| Previous by Thread: | Re: right way to report bugs, Jan Derfinak |
| Next by Thread: | Re: right way to report bugs, Jan Derfinak |
| Indexes: | [Date] [Thread] [Top] [All Lists] |