From: TR Reardon <thomas_reardon@hotmail.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: resize2fs problem with stride calc
Date: Sat, 20 Sep 2014 16:46:36 -0400 [thread overview]
Message-ID: <BAY179-W85AF983234DB78F07A12EFDB50@phx.gbl> (raw)
resize2fs seems to come up with some crazy default stride numbers. This occurs with and without bigalloc.
I was testing enabling/disabling 64bit using latest patches from DJW, and noticed that s_raid_stride was being written with nonsensical values, in particular determine_fs_stride() is coming up with overly large values. The code is old (2006) and lacks comment so I'm not sure what the intended operation is. Does this just need to be updated for flex_bg? Should s_raid_stride ever be auto-changed on resize? If it should change, should stripe also change?
+Reardon
next reply other threads:[~2014-09-20 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 20:46 TR Reardon [this message]
2014-09-21 16:13 ` resize2fs problem with stride calc Eric Sandeen
2014-09-21 22:32 ` TR Reardon
2014-09-29 20:59 ` Darrick J. Wong
2014-09-29 22:46 ` 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=BAY179-W85AF983234DB78F07A12EFDB50@phx.gbl \
--to=thomas_reardon@hotmail.com \
--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