Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-16 Thread dann frazier
On Sat, Jul 14, 2018 at 5:21 AM dann frazier wrote: > > On Thu, Jul 12, 2018 at 5:08 PM Theodore Y. Ts'o wrote: > > > > > > > > Review console log and on each run I have filesystem rebuild. The problem > > > is that mke2fs I am using is 1.44.3-rc2. I am now reseting the environment > > > and re-t

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-14 Thread dann frazier
On Thu, Jul 12, 2018 at 5:08 PM Theodore Y. Ts'o wrote: > > > > > Review console log and on each run I have filesystem rebuild. The problem > > is that mke2fs I am using is 1.44.3-rc2. I am now reseting the environment > > and re-test. > > > > Could it be that you saw the error in ext4_validate_bl

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-12 Thread Theodore Y. Ts'o
> > Review console log and on each run I have filesystem rebuild. The problem > is that mke2fs I am using is 1.44.3-rc2. I am now reseting the environment > and re-test. > Could it be that you saw the error in ext4_validate_block_bitmap()? The patch which I sent Dann only fixed the problem for in

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-11 Thread Ike Panhc
On 07/11/2018 04:43 AM, dann frazier wrote: > On Tue, Jul 10, 2018 at 10:51:43AM -0600, dann frazier wrote: >> On Sat, Jul 07, 2018 at 12:10:18AM -0400, Theodore Y. Ts'o wrote: >>> On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote: Hi, We're seeing a regression triggered by t

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-10 Thread dann frazier
On Tue, Jul 10, 2018 at 10:51:43AM -0600, dann frazier wrote: > On Sat, Jul 07, 2018 at 12:10:18AM -0400, Theodore Y. Ts'o wrote: > > On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote: > > > Hi, > > > We're seeing a regression triggered by the stress-ng[*] "chdir" test > > > that I've

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-10 Thread dann frazier
On Sat, Jul 07, 2018 at 12:10:18AM -0400, Theodore Y. Ts'o wrote: > On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote: > > Hi, > > We're seeing a regression triggered by the stress-ng[*] "chdir" test > > that I've bisected to: > > > > 044e6e3d74a3 ext4: don't update checksum of new in

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-06 Thread Theodore Y. Ts'o
On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote: > Hi, > We're seeing a regression triggered by the stress-ng[*] "chdir" test > that I've bisected to: > > 044e6e3d74a3 ext4: don't update checksum of new initialized bitmaps > > So far we've only seen failures on servers based on HiS

[Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-06 Thread dann frazier
Hi, We're seeing a regression triggered by the stress-ng[*] "chdir" test that I've bisected to: 044e6e3d74a3 ext4: don't update checksum of new initialized bitmaps So far we've only seen failures on servers based on HiSilicon's family of ARM64 SoCs (D05/Hi1616 SoC, D06/Hi1620 SoC). On these sys