From: Jay Ashworth <jra@baylink.com>
To: xfs@oss.sgi.com
Subject: Re: Default mkfs parms for my DVR drive
Date: Sat, 24 Aug 2013 20:41:05 -0400 (EDT) [thread overview]
Message-ID: <4336525.4942.1377391265287.JavaMail.root@benjamin.baylink.com> (raw)
In-Reply-To: <52194911.3050606@gmail.com>
---- Original Message -----
> From: "Joe Landman" <joe.landman@gmail.com>
> 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.
Well, if I can't; they're the ones who screwed up. :-)
> 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.
Ok, ok; this isn't the same thread anymore. :-)
Linux duckling 3.4.47-2.38-default #1 SMP Fri May 31 20:17:40 UTC 2013 (3961086) i686 athlon i386 GNU/Linux
> Your hardware could also be somewhat slow ... Could you do an
>
> lshw -class disk -class storage
It probably is.
It's an old Athlon, MSI MS-7021, KT6V chipset; 512M of DDR... maybe that's
DDR 2; it won't run right with more.
I don't seem to have lshw.
Or, oddly, hwconfig. It's got 3 Seagate ST3000DM001s, 2 on a SiI 7114 PCI
with a pair of Fujitsu Deskstars, 2T and 1T; 40G Samsung boot on the mobo SATA;
the third 3000 is in a USB 2 enclosure.
And this latest rsync has gotten 78G and then paused; 80G and then paused....
84G and then paused...
5 min LA 1.9, and the rsync is the top process.
I have smartd running; no errors yet.
Still watching...
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra@baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-25 0:41 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
2013-08-25 0:41 ` Jay Ashworth [this message]
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=4336525.4942.1377391265287.JavaMail.root@benjamin.baylink.com \
--to=jra@baylink.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