From: Joe Landman <joe.landman@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: Default mkfs parms for my DVR drive
Date: Sat, 24 Aug 2013 20:00:17 -0400 [thread overview]
Message-ID: <52194911.3050606@gmail.com> (raw)
In-Reply-To: <1365641.4934.1377388085878.JavaMail.root@benjamin.baylink.com>
On 08/24/2013 07:48 PM, Jay Ashworth wrote:
> This is a Seagate ST3000DM001, all one volume, for my sister's DVR on
> which I've been doing this volume recovery work. The default setup that
> mkfs.xfs returns with no parms supplies is this:
>
> meta-data=/dev/sda1 isize=256 agcount=4, agsize=183141568 blks
> = sectsz=4096 attr=2, projid32bit=0
> data = bsize=4096 blocks=732566272, imaxpct=5
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal log bsize=4096 blocks=357698, version=2
> = sectsz=4096 sunit=1 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> and that takes about 3 minutes to mkfs a 3TB drive.
>
> Anyone have some thoughts they wish to cast upon the waters about either part
> of that?
Dave, Eric, and the rest of the xfs team will tell you "use the defaults
Luke". For 99 and 44/100ths percent of users, this is the right choice.
I am guessing that some of the delay may be the speed of the interface
to the disk ... but even then 3 minutes sounds long, unless something
else is hitting the disk at the same time.
Which kernel version btw? A quick 'uname -a' is a good thing.
Your hardware could also be somewhat slow ... Could you do an
lshw -class disk -class storage
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-25 0:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29874428.3384.1376259762936.JavaMail.root@benjamin.baylink.com>
2013-08-11 22:36 ` XFS recovery resumes Jay Ashworth
2013-08-18 21:38 ` Jay Ashworth
2013-08-18 21:51 ` Joe Landman
2013-08-18 22:11 ` Jay Ashworth
2013-08-18 22:57 ` Joe Landman
2013-08-18 23:21 ` Jay Ashworth
2013-08-18 22:06 ` Stan Hoeppner
2013-08-19 3:55 ` Jay Ashworth
2013-08-19 6:47 ` Stan Hoeppner
2013-08-24 23:43 ` Jay Ashworth
2013-08-25 3:44 ` Stan Hoeppner
2013-08-25 15:29 ` Jay Ashworth
2013-08-25 17:45 ` Stan Hoeppner
2013-08-25 20:27 ` Jay Ashworth
2013-08-26 5:45 ` Stan Hoeppner
2013-08-26 15:42 ` Jay Ashworth
2013-08-24 23:48 ` Default mkfs parms for my DVR drive Jay Ashworth
2013-08-25 0:00 ` Joe Landman [this message]
2013-08-25 0:41 ` Jay Ashworth
2013-08-25 3:41 ` Jay Ashworth
2013-08-22 9:16 ` XFS recovery resumes Stefan Ring
2013-08-27 23:59 ` Dave Chinner
2013-08-28 0:19 ` Jay Ashworth
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=52194911.3050606@gmail.com \
--to=joe.landman@gmail.com \
--cc=xfs@oss.sgi.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