From: zhangyi (F)
commit 7b97d868b7ab2448859668de9222b8af43f76e78 upstream.
In the ext4 filesystem with errors=panic, if one process is recording
errno in the superblock when invoking jbd2_journal_abort() due to some
error cases, it could be raced by another __ext4_abort() which is
setting the S
On Mon, Aug 22, 2016 at 10:33:08AM +0300, Török Edwin wrote:
> On 2016-08-18 02:28, Darrick J. Wong wrote:
> > On Wed, Aug 17, 2016 at 05:27:25PM +0300, Török Edwin wrote:
> >> On 2016-08-08 09:28, Darrick J. Wong wrote:
> >>> On Sun, Aug 07, 2016 at 11:56:34PM -0400, Theodore Ts'o wrote:
> On
On 2016-08-18 02:28, Darrick J. Wong wrote:
> On Wed, Aug 17, 2016 at 05:27:25PM +0300, Török Edwin wrote:
>> On 2016-08-08 09:28, Darrick J. Wong wrote:
>>> On Sun, Aug 07, 2016 at 11:56:34PM -0400, Theodore Ts'o wrote:
On Fri, Aug 05, 2016 at 12:15:48PM -0700, Darrick J. Wong wrote:
>>>
On 2016-08-17 23:02, Johannes Stezenbach wrote:
> On Fri, Aug 05, 2016 at 08:11:36PM +0200, Johannes Stezenbach wrote:
>> On Fri, Aug 05, 2016 at 10:02:28AM -0700, Darrick J. Wong wrote:
>>>
>>> When you're back on 4.7, can you apply this patch[1] to see if it fixes
>>> the problem? I speculate th
On Wed, Aug 17, 2016 at 05:27:25PM +0300, Török Edwin wrote:
> On 2016-08-08 09:28, Darrick J. Wong wrote:
> > On Sun, Aug 07, 2016 at 11:56:34PM -0400, Theodore Ts'o wrote:
> >> On Fri, Aug 05, 2016 at 12:15:48PM -0700, Darrick J. Wong wrote:
> > [1]
> > https://git.kernel.org/cgit/linux/
On Fri, Aug 05, 2016 at 08:11:36PM +0200, Johannes Stezenbach wrote:
> On Fri, Aug 05, 2016 at 10:02:28AM -0700, Darrick J. Wong wrote:
> >
> > When you're back on 4.7, can you apply this patch[1] to see if it fixes
> > the problem? I speculate that the new parallel dir lookup code enables
> > mu
On 2016-08-08 09:28, Darrick J. Wong wrote:
> On Sun, Aug 07, 2016 at 11:56:34PM -0400, Theodore Ts'o wrote:
>> On Fri, Aug 05, 2016 at 12:15:48PM -0700, Darrick J. Wong wrote:
> [1]
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/ext4/inode.c?id=b47820edd1634dc
On 2016-08-09 05:37, Darrick J. Wong wrote:
> On Tue, Aug 09, 2016 at 12:13:01AM +0300, Török Edwin wrote:
>> On 2016-08-08 19:55, Darrick J. Wong wrote:
>>> On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote:
On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote:
>
>>
On Tue, Aug 09, 2016 at 12:13:01AM +0300, Török Edwin wrote:
> On 2016-08-08 19:55, Darrick J. Wong wrote:
> > On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote:
> >> On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote:
> >>>
> >>> I have one lingering concern -- is it a bug
On 2016-08-08 19:55, Darrick J. Wong wrote:
> On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote:
>> On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote:
>>>
>>> I have one lingering concern -- is it a bug that two processes could be
>>> computing the checksum of a buffer sim
On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote:
> On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote:
> >
> > I have one lingering concern -- is it a bug that two processes could be
> > computing the checksum of a buffer simultaneously? I would have thought
> > ext4
>
On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote:
>
> I have one lingering concern -- is it a bug that two processes could be
> computing the checksum of a buffer simultaneously? I would have thought ext4
> would serialize that kind of buffer_head access...
Do we know how this is
On Sun, Aug 07, 2016 at 11:56:34PM -0400, Theodore Ts'o wrote:
> On Fri, Aug 05, 2016 at 12:15:48PM -0700, Darrick J. Wong wrote:
> > > > [1]
> > > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/ext4/inode.c?id=b47820edd1634dc1208f9212b7ecfb4230610a23
> > >
> > > I ad
On Fri, Aug 05, 2016 at 12:15:48PM -0700, Darrick J. Wong wrote:
> > > [1]
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/ext4/inode.c?id=b47820edd1634dc1208f9212b7ecfb4230610a23
> >
> > I added the patch, rebuilt and rebooted. It will take some time
> > before I
On Fri, Aug 05, 2016 at 08:11:36PM +0200, Johannes Stezenbach wrote:
> On Fri, Aug 05, 2016 at 10:02:28AM -0700, Darrick J. Wong wrote:
> > On Fri, Aug 05, 2016 at 12:35:44PM +0200, Johannes Stezenbach wrote:
> > > On Wed, Aug 03, 2016 at 05:50:26PM +0300, Török Edwin wrote:
> > > > I have just enc
On Fri, Aug 05, 2016 at 10:02:28AM -0700, Darrick J. Wong wrote:
> On Fri, Aug 05, 2016 at 12:35:44PM +0200, Johannes Stezenbach wrote:
> > On Wed, Aug 03, 2016 at 05:50:26PM +0300, Török Edwin wrote:
> > > I have just encountered a similar problem after I've recently upgraded to
> > > 4.7.0:
> >
On Fri, Aug 05, 2016 at 12:35:44PM +0200, Johannes Stezenbach wrote:
> On Wed, Aug 03, 2016 at 05:50:26PM +0300, Török Edwin wrote:
> > I have just encountered a similar problem after I've recently upgraded to
> > 4.7.0:
> > [Wed Aug 3 11:08:57 2016] EXT4-fs error (device dm-1): dx_probe:740: ino
On Wed, Aug 03, 2016 at 05:50:26PM +0300, Török Edwin wrote:
> I have just encountered a similar problem after I've recently upgraded to
> 4.7.0:
> [Wed Aug 3 11:08:57 2016] EXT4-fs error (device dm-1): dx_probe:740: inode
> #13295: comm python: Directory index failed checksum
> [Wed Aug 3 11:0
Hi,
I have just encountered a similar problem after I've recently upgraded to 4.7.0:
[Wed Aug 3 11:08:57 2016] EXT4-fs error (device dm-1): dx_probe:740: inode
#13295: comm python: Directory index failed checksum
[Wed Aug 3 11:08:57 2016] Aborting journal on device dm-1-8.
[Wed Aug 3 11:08:57
On Mon, Jul 18, 2016 at 04:17:23PM +0200, Johannes Stezenbach wrote:
> On Mon, Jul 18, 2016 at 09:38:43AM -0400, Theodore Ts'o wrote:
> > On Mon, Jul 18, 2016 at 12:57:07PM +0200, Johannes Stezenbach wrote:
> > >
> > > I'm running 4.7.0-rc7 with ext4 on lvm on dm-crypt on SSD
> > > and out of the
On Mon, Jul 18, 2016 at 09:38:43AM -0400, Theodore Ts'o wrote:
> On Mon, Jul 18, 2016 at 12:57:07PM +0200, Johannes Stezenbach wrote:
> >
> > I'm running 4.7.0-rc7 with ext4 on lvm on dm-crypt on SSD
> > and out of the blue on idle machine the following error
> > message appeared:
> >
> > [373851
On Mon, Jul 18, 2016 at 12:57:07PM +0200, Johannes Stezenbach wrote:
>
> I'm running 4.7.0-rc7 with ext4 on lvm on dm-crypt on SSD
> and out of the blue on idle machine the following error
> message appeared:
>
> [373851.683131] EXT4-fs (dm-3): error count since last fsck: 1
> [373851.683151] EXT
Hi,
I'm running 4.7.0-rc7 with ext4 on lvm on dm-crypt on SSD
and out of the blue on idle machine the following error
message appeared:
[373851.683131] EXT4-fs (dm-3): error count since last fsck: 1
[373851.683151] EXT4-fs (dm-3): initial error at time 1468438194: dx_probe:740:
inode 22288562
[3
On Wed, Apr 13, 2016 at 01:44:55PM +, Eric Shang wrote:
> HI All:
> I meet an ext4 error, following is the error log. After panic, I check the
> emmc by the tool debufs, the inode 69878 i_nlink is not zero. And this inode
> don't belong to parent dir 6987, it belong t
; adilger.ker...@dilger.ca; linux-nvd...@lists.01.org;
linux-fsde...@vger.kernel.org; linux-e...@vger.kernel.org; x...@oss.sgi.com;
linux-kernel@vger.kernel.org
主题: Re: ext4 error
On Wed, 2016-04-13 at 13:44 +, Eric Shang wrote:
> HI All:
> I meet an ext4 error, following is the error log. After
On Wed, 2016-04-13 at 13:44 +, Eric Shang wrote:
> HI All:
> I meet an ext4 error, following is the error log. After panic, I check the
> emmc by the tool debufs, the inode 69878 i_nlink is not zero. And this inode
> don't belong to parent dir 6987, it belong to other file(
HI All:
I meet an ext4 error, following is the error log. After panic, I check the
emmc by the tool debufs, the inode 69878 i_nlink is not zero. And this inode
don't belong to parent dir 6987, it belong to other file(this inode belong to
two files when check by debugfs ncheck), I guess
27 matches
Mail list logo
