On Thu, 14 Sep 2006, Barry Naujok wrote:
> > Still, xfs_check reported:
> > => link count mismatch for inode 400254 (name ?), nlink 0, counted 2
> > => link count mismatch for inode 4239409 (name ?), nlink 0, counted 2
> > => link count mismatch for inode 8388736 (name ?), nlink 39,
> > counted 3
Nathan Scott <[EMAIL PROTECTED]> writes:
> On Tue, Sep 12, 2006 at 12:30:08AM +0200, Ferenc Wagner wrote:
>> Package: xfsprogs
>> Version: 2.8.11-1
>> Severity: normal
>>
>> I guess my problem is rooted in the 'well known' 2.6.17 error, or maybe
>> not. Anyway, my experience under a current Sid
On Tue, Sep 12, 2006 at 12:30:08AM +0200, Ferenc W?gner wrote:
> Package: xfsprogs
> Version: 2.8.11-1
> Severity: normal
>
> Hi,
>
> I guess my problem is rooted in the 'well known' 2.6.17 error, or maybe
> not. Anyway, my experience under a current Sid system is that
> xfs_repair does not fix
Package: xfsprogs
Version: 2.8.11-1
Severity: normal
Hi,
I guess my problem is rooted in the 'well known' 2.6.17 error, or maybe
not. Anyway, my experience under a current Sid system is that
xfs_repair does not fix my filesystem. It does something, as the first
two runs produced slightly differ
4 matches
Mail list logo