| To: | "Alfred G. de Wijn" <dwijn@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: problem with xfs_fsr |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Wed, 9 Apr 2003 14:28:45 -0700 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030407051232.GA1711@iluvatar.eu.org> |
| References: | <20030407051232.GA1711@iluvatar.eu.org> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Mon, Apr 07, 2003 at 07:12:33AM +0200, Alfred G. de Wijn wrote: > Anyway, I asked on #XFS, and recompiled a brand new kernel. Same > behaviour. I tried without the binary nvidia driver. Same > behaviour. What kernel versions did you try? > I can provide both a kernel config and hexdumps of a healthy and a > borked logfile on demand. I also tried to file a bugreport, but > bugzilla didn't send me an email with my password. Being reproducable is the main thing. Otherwise it's hard to track down. --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs for solaris?, Chris Wedgwood |
|---|---|
| Next by Date: | Re: xfsrepair: rebuilding directory inode 128, Chris Wedgwood |
| Previous by Thread: | Re: problem with xfs_fsr, Wessel Dankers |
| Next by Thread: | Re: problem with xfs_fsr, Alfred G. de Wijn |
| Indexes: | [Date] [Thread] [Top] [All Lists] |