From: Chris Hunter <chris.hunter@yale.edu>
To: linux-ext4@vger.kernel.org
Subject: errors following ext3 to ext4 conversion
Date: Wed, 26 Aug 2015 20:53:13 -0400 [thread overview]
Message-ID: <55DE5F79.4010004@yale.edu> (raw)
I attempted to convert ext3 to ext4 filesystem. I am using e2fsprogs
(1.42.12.wc1 (15-Sep-2014)). I ran command tune2fs tune2fs -O
extents,uninit_bg,dir_index /dev/DEV -o acl,user_xattr /dev/DEV.
I then encountered errors (below) when running read-only e2fsck. I have
not mounted the filesystem.
Is it possible to backout the ext3/ext4 changes ?
Do tune2fs changes take effect immediately or next time filesystem is
mounted?
e2fsck shows a variety of errors:
Pass 1: Checking inodes, blocks, and sizes
Inode 118843400, end of extent exceeds allowed value
(logical block 1409, physical block 3803034390, len 976)
Inode 118843400, end of extent exceeds allowed value
(logical block 2385, physical block 3803056554, len 4294966945)
Inode 118843400, i_size is 8331264, should be 5771264. Fix? no
Inode 118843400, i_blocks is 16328, should be 11312. Fix? no
(...)
Pass 2: Checking directory structure
Problem in HTREE directory inode 118843400 (/O/0/d0): bad block number 2030.
Problem in HTREE directory inode 118843400 (/O/0/d0): bad block number 2031.
Problem in HTREE directory inode 118843400 (/O/0/d0): bad block number 2032.
Problem in HTREE directory inode 118843400 (/O/0/d0): bad block number 2033.
Pass 4: Checking reference counts
Unattached inode 26
Unattached inode 27
Unattached inode 28
regards,
chris hunter
chris.hunter@yale.edu
next reply other threads:[~2015-08-27 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 0:53 Chris Hunter [this message]
2015-08-27 3:39 ` errors following ext3 to ext4 conversion Theodore Ts'o
2015-08-27 3:43 ` Eric Sandeen
2015-08-27 4:15 ` Darrick J. Wong
2015-08-27 18:58 ` Theodore Ts'o
2015-08-27 19:28 ` Chris Hunter
2015-08-27 22:46 ` Theodore Ts'o
2015-08-28 16:23 ` Chris Hunter
2015-08-28 18:32 ` Theodore Ts'o
2015-08-27 21:34 ` Eric Sandeen
2015-08-28 16:09 ` Andreas Dilger
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=55DE5F79.4010004@yale.edu \
--to=chris.hunter@yale.edu \
--cc=linux-ext4@vger.kernel.org \
/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