From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Theodore Ts'o'" <tytso@mit.edu>,
"'Calvin Walton'" <calvin.walton@kepstin.ca>, <ap@solarrain.com>
Cc: "'Andreas Dilger'" <adilger@dilger.ca>,
"'Javier Marcet'" <jmarcet@gmail.com>,
"'Linux Ext4 Mailing List'" <linux-ext4@vger.kernel.org>
Subject: RE: Far too long mount time
Date: Fri, 17 Aug 2012 11:00:19 -0400 [thread overview]
Message-ID: <018a01cd7c89$05687cf0$103976d0$@lucidpixels.com> (raw)
In-Reply-To: <018901cd7c87$515904b0$f40b0e10$@lucidpixels.com>
-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
Sent: Friday, August 17, 2012 10:48 AM
To: 'Theodore Ts'o'; 'Calvin Walton'; ap@solarrain.com
Cc: 'Andreas Dilger'; 'Javier Marcet'; 'Linux Ext4 Mailing List'
Subject: RE: Far too long mount time
-----Original Message-----
From: Theodore Ts'o [mailto:tytso@mit.edu]
Sent: Friday, August 17, 2012 9:55 AM
To: Calvin Walton
Cc: Andreas Dilger; Javier Marcet; Linux Ext4 Mailing List;
jpiszcz@lucidpixels.com
Subject: Re: Far too long mount time
On Thu, Aug 16, 2012 at 02:53:37PM -0400, Theodore Ts'o wrote:
> This patch should solve the problem (as an alternative to reverting
> 8aeb00ff85a).
This should be "grp"; stupid typo on my part.
This patch with the fix-up will be pushed to Linus shortly and tagged
for the stable tree.
--
Hi Theo,
Found the patch here:
http://www.spinics.net/lists/linux-ext4/msg33498.html
Patched against the fresh+stable 3.5.1 tree:
p34:/usr/src/linux-3.5.1# patch -p1 < ../tso.patch
patching file fs/ext4/super.c
Hunk #1 succeeded at 3109 (offset -20 lines).
p34:/usr/src/linux-3.5.1#
Rebooted, but we have a problem, my 60TB RAID-6 is now a 46TB RAID-6?
I am rebooting back into the 3.5.1+earlier reverted patch.
p34:~# uptime; uname -a ; df -h | grep /r1
10:46:51 up 0 min, 1 user, load average: 1.04, 0.27, 0.09
Linux p34 3.5.1 #5 SMP Fri Aug 17 10:24:22 EDT 2012 x86_64 GNU/Linux
/dev/sda1 46T 1.5T 45T 4% /r1
p34:~#
--
Went back to old kernel (w/reverted patch, it is ok now)
p34:~# uname -a; uptime; df -h |grep /r1
Linux p34 3.5.1+ #3 SMP Sun Aug 12 10:31:34 EDT 2012 x86_64 GNU/Linux
10:59:51 up 9 min, 1 user, load average: 0.00, 0.20, 0.23
/dev/sda1 61T 16T 45T 27% /r1
p34:~#
Justin.
next prev parent reply other threads:[~2012-08-17 15:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAnFQG_O051svcCZftDefebVEds+P1zAceteh=B18HOqmoqitg@mail.gmail.com>
2012-08-16 7:54 ` Fwd: Far too long mount time Javier Marcet
2012-08-16 9:09 ` Andreas Dilger
2012-08-16 9:18 ` Javier Marcet
2012-08-16 9:53 ` Javier Marcet
2012-08-16 14:16 ` Calvin Walton
2012-08-16 14:42 ` Theodore Ts'o
2012-08-16 18:53 ` Theodore Ts'o
2012-08-16 19:23 ` Eric Sandeen
2012-08-16 19:57 ` Theodore Ts'o
2012-08-17 13:55 ` Theodore Ts'o
2012-08-17 14:48 ` Justin Piszcz
2012-08-17 14:58 ` Theodore Ts'o
2012-08-17 15:00 ` Justin Piszcz [this message]
2012-08-17 15:13 ` Theodore Ts'o
2012-08-17 15:27 ` Theodore Ts'o
2012-08-17 19:18 ` Justin Piszcz
2012-08-17 19:44 ` Eric Sandeen
2012-08-17 15:58 ` 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='018a01cd7c89$05687cf0$103976d0$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=adilger@dilger.ca \
--cc=ap@solarrain.com \
--cc=calvin.walton@kepstin.ca \
--cc=jmarcet@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).