xfs
[Top] [All Lists]

Re: right way to report bugs

To: Jan Derfinak <ja@xxxxxxxxxxxx>
Subject: Re: right way to report bugs
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Mon, 12 Dec 2005 12:49:34 -0600
Cc: linux-xfs@xxxxxxxxxxx, overby@xxxxxxx
In-reply-to: <Pine.LNX.4.61.0512121150540.11817@darkAngel.home.sk>
References: <Pine.LNX.4.61.0512121150540.11817@darkAngel.home.sk>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720)
Jan Derfinak wrote:
Please tell me the right way to report xfs problems which I should use.

jan


I think you've got it - file a bug, and harrass the list if no response :)

In the past I have used xfs_db to change the nblocks or nextents for this inode to match (usually both 0), and re-run repair. Not the best solution I know, but one possible way out of the problem.

The unmounting message is confusing; it's a result of using some of the same code in kernelspace & userspace.

But in this case, it's xfs_repair's job to fix inconsistent things; I don't know why it bails out on this one. We've found a couple of other cases like this recently as well.

-Eric


<Prev in Thread] Current Thread [Next in Thread>