linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: TR Reardon <thomas_reardon@hotmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: journal recovery problems with metadata_csum, *non-64bit*
Date: Fri, 8 Aug 2014 15:15:48 -0700	[thread overview]
Message-ID: <20140808221548.GE11191@birch.djwong.org> (raw)
In-Reply-To: <BLU436-SMTP84585FAA628776E190822AFDEE0@phx.gbl>

On Fri, Aug 08, 2014 at 03:31:12PM -0400, TR Reardon wrote:
> Kernel 3.16, e2fsprogs 1.43-WIP (1.42.11 compiled with metadata_csum
> support), filesystems mounted with journal_async_commit.
> 
> This may be an fsck problem, hard to tell.  I consistently have
> problems with journal recovery after hard reboot when filesystem has
> metadata_csum.   Interestingly, no problems with 64-bit filesystems.
> 
> during journal replay, bogus block numbers are reported.  in this
> case, a 128MB file was deleted on two filesystems where the only
> difference is 64bit vs non-64bit.  This also happens with or without
> bigalloc, though I only document bigalloc case here.

Could you post full logs, including the bogus block numbers, please?  I've a
suspicion that we might be mishandling the 32/64 bit switch in either the
descriptor block or the revocation block, but it's hard to tell from the five
lines of log.

--D
> 
> please see attached superblocks, dumped just prior to hard reboot.
> disk8=sdm1, disk9=sdn1
> 
> dmesg:
> 
> [Fri Aug  8 15:16:28 2014] JBD2: Out of memory during recovery.
> [Fri Aug  8 15:16:28 2014] JBD2: recovery failed
> [Fri Aug  8 15:16:28 2014] EXT4-fs (sdm1): error loading journal
> [Fri Aug  8 15:16:27 2014] EXT4-fs (sdn1): recovery complete
> [Fri Aug  8 15:16:27 2014] EXT4-fs (sdn1): mounted filesystem with
> ordered data mode. Opts: journal_async_commit
> 
> 
> fsck:
> 
> #e2fsck -f -v /dev/sdm1
> e2fsck 1.43-WIP (09-Jul-2014)
> disk8: recovering journal
> Error writing block 549755813991 (Invalid argument).  Ignore error<y>? yes
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> Free blocks count wrong (11332304, counted=11365072).
> Fix<y>? yes
> Free inodes count wrong (177287, counted=177288).
> Fix<y>? yes
> 
> disk8: ***** FILE SYSTEM WAS MODIFIED *****
> 
>         1656 inodes used (0.93%, out of 178944)
>          260 non-contiguous files (15.7%)
>            0 non-contiguous directories (0.0%)
>              # of inodes with ind/dind/tind blocks: 0/0/0
>              Extent depth histogram: 1280/363/5
>    721201312 blocks used (98.45%, out of 732566384)
>            0 bad blocks
>          358 large files
> 
>         1267 regular files
>          380 directories
>            0 character device files
>            0 block device files
>            0 fifos
>            0 links
>            0 symbolic links (0 fast symbolic links)
>            0 sockets
> ------------
>         1647 files




  parent reply	other threads:[~2014-08-08 22:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 19:31 journal recovery problems with metadata_csum, *non-64bit* TR Reardon
2014-08-08 21:47 ` Theodore Ts'o
2014-08-08 22:29   ` TR Reardon
2014-08-09  0:21     ` Theodore Ts'o
     [not found]       ` <BLU436-SMTP1726DA8B9CB511781B73155FDEF0@phx.gbl>
2014-08-09  4:07         ` Theodore Ts'o
2014-08-08 22:15 ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-10 22:35 TR Reardon
     [not found] <BLU437-SMTP3407533C3883653626BD3DFDEC0@phx.gbl>
2014-08-11  7:10 ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140808221548.GE11191@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=thomas_reardon@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).