lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070316195951.GB5743@melbourne.sgi.com>
Date:	Sat, 17 Mar 2007 06:59:51 +1100
From:	David Chinner <dgc@....com>
To:	Marco Berizzi <pupilla@...mail.com>
Cc:	David Chinner <dgc@....com>, linux-kernel@...r.kernel.org,
	xfs@....sgi.com
Subject: Re: XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c.  Caller 0xc01b00bd

On Fri, Mar 16, 2007 at 12:05:33PM +0100, Marco Berizzi wrote:
> David Chinner wrote:
> 
> > can
> > you post a url to the commit?
> 
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.19.y.git;a=commit;h=7fbbb01dca7704d52ace6f45a805c98a5b0362f9

Ok, so an ipsec change. And I see from the history below it
really has nothing to do with this problem. it seems the problem
has something to do with changes between 2.6.19.1 and 2.6.19.2.

There were no changes to XFS between 2.6.19.1 and 2.6.19.2,
so I'm thinking that your problems are related to something
other than XFS. Can you do a git bisect to determine what the
bad patch is?

> > Can you run xfs_repair on that filesystem and see if reports
> > (and fixes) any problems?
> 
> I don't need to run xfs_repair to fix the problem,

Except that the trigger might be on-disk corruption so we
need to rule that out first.

> I only unplug the power cable and reboot the system,
> xfs filesystem are correctly mounted.
> However tell me if I must run xfs_repair to check
> the filesystem.

Yes, you need to run xfs_repair.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ