linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "cheater00 ." <cheater00@gmail.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Liu Bo <bo.li.liu@oracle.com>, Henk Slager <hslager@hotmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Bad fs performance, IO freezes
Date: Fri, 6 Nov 2015 14:37:11 +0100	[thread overview]
Message-ID: <CA+9GZUhgVBzfdowkR_EagSdsN5HNGi_uPQM=AE2TeWQQ0idymQ@mail.gmail.com> (raw)
In-Reply-To: <56327B01.7010002@gmail.com>

I am getting a sata dock for my laptop next week. Until then, is it
possible to perform an action in btrfs (like rm which seems to trigger
the issue) and make it log what exactly it's doing?


On Thu, Oct 29, 2015 at 9:01 PM, Austin S Hemmelgarn
<ahferroin7@gmail.com> wrote:
> On 2015-10-29 11:49, cheater00 . wrote:
>>
>> Hi Austin,
>> seek times are fine, but this literally freezes my computer for a
>> split second. I've had to re-type this email twice because the freezes
>> meant letters I typed would not arrive on the screen.
>> USB disks are so common they should not be having issues.
>
> That's debatable.  USB is commonly used because it's almost impossible to
> find a system that doesn't have it, not because it's reliable.  The original
> intent was for it to be used for stuff like mice and keyboards, so it was
> designed with low-latency and fair scheduling in mind, both of which really
> hurt performance of bulk data storage devices.
>>
>> I have 4.3.0-040300rc7-generic #201510260712 which is just three days old.
>
> That should be perfectly recent enough, although FWIW, the official version
> of 4.3 should be out this Sunday.
>>
>>
>> Please advise. Isn't it better to *not* use a vm to debug this?
>
> That depends.  For something like this, it could go either way.  I just use
> a VM because that's what I always use, because it's nice not crashing your
> system when trying to debug a kernel panic.
>>
>> BTW, if we are talking about slow speed making things worse, I could
>> try downgrading the cable to usb2.
>> Is there a standard virtualbox VM that I could use?
>
> In general, it's pretty easy to set something like Ubuntu up in VirtualBox,
> the install is essentially identical to regular hardware aside from the
> initial setup of the VM itself.  The documentation for VirtualBox is really
> good, if you've never used virtualization before, it's definitely worth
> reading.
>>
>> I'll download Gentoo in the meantime. I have never used it. I'm
>> getting the "minimal installation cd" from 29th september.
>>
>> http://distfiles.gentoo.org/releases/x86/autobuilds/20150929/install-x86-minimal-20150929.iso
>
> I meant by no means that you needed to use Gentoo, I only mentioned it
> because it's what I use (which in turn is because that's what I use on just
> about everything except stuff like the Raspberry Pi or the BeagleBoard).  If
> you just want to debug this and then be done with it, I would actually
> advise against using Gentoo, it takes a lot of effort to get a system up and
> running with it, and it's very involved to maintain compared to Ubuntu.  On
> the other hand though, if you are willing to learn to use it, it's one of
> the most highly customizable Linux distros out there, and can have
> noticeably better performance than more generic distros (FWIW, it's also one
> of the last big distros that doesn't force systemd on it's users by
> default).
>

      reply	other threads:[~2015-11-06 13:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 12:16 Bad fs performance, IO freezes cheater00 .
2015-10-26 13:32 ` Donald Pearson
2015-10-26 13:36   ` cheater00 .
2015-10-26 13:45     ` Donald Pearson
2015-10-26 13:46       ` cheater00 .
2015-10-26 13:56         ` cheater00 .
2015-10-26 14:00           ` Donald Pearson
2015-10-26 14:25 ` Liu Bo
2015-10-26 14:38   ` cheater00 .
2015-10-26 15:40     ` cheater00 .
2015-10-26 17:43       ` cheater00 .
2015-10-26 18:31         ` cheater00 .
2015-10-27  2:00           ` cheater00 .
2015-10-27  6:39             ` Duncan
2015-10-27  8:55               ` cheater00 .
2015-10-27 11:44             ` Austin S Hemmelgarn
2015-10-27 13:00               ` Henk Slager
2015-10-27 13:30                 ` Austin S Hemmelgarn
2015-10-27 14:22                   ` cheater00 .
2015-10-27 14:26                     ` cheater00 .
2015-10-27 14:30                       ` cheater00 .
2015-10-27 14:43                         ` cheater00 .
2015-10-27 15:01                           ` Holger Hoffstätte
2015-10-27 15:05                             ` cheater00 .
2015-10-27 15:07                               ` cheater00 .
2015-10-27 15:22                                 ` Holger Hoffstätte
2015-10-27 15:26                           ` Austin S Hemmelgarn
2015-10-29 13:03                             ` cheater00 .
2015-10-29 14:00                               ` Austin S Hemmelgarn
2015-10-29 15:49                                 ` cheater00 .
2015-10-29 18:49                                   ` Henk Slager
2015-10-29 20:01                                   ` Austin S Hemmelgarn
2015-11-06 13:37                                     ` cheater00 . [this message]

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='CA+9GZUhgVBzfdowkR_EagSdsN5HNGi_uPQM=AE2TeWQQ0idymQ@mail.gmail.com' \
    --to=cheater00@gmail.com \
    --cc=ahferroin7@gmail.com \
    --cc=bo.li.liu@oracle.com \
    --cc=hslager@hotmail.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).