All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 194511] New: filesystem slow down
Date: Wed, 08 Feb 2017 16:05:32 +0000	[thread overview]
Message-ID: <bug-194511-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=194511

            Bug ID: 194511
           Summary: filesystem slow down
           Product: File System
           Version: 2.5
    Kernel Version: 4.4.44 und 4.8.???
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
          Assignee: fs_ext3@kernel-bugs.osdl.org
          Reporter: dieter.ferdinand@gmx.de
        Regression: No

hello,
last month i try to update to the last kernel 4.4.xx. but that was a big fault.

after the update, it looks fine, but after some time (ca 30 minutes after a
restart of the server, the system slow down and i need to much time to copy
files to the drives.

i test the speed:
read usb >30000 MB/s
read sata >100000MB/s
write filesystem usb ca 1 MB/s
write filesystem sata ca 1 MB/s

this month i used a rescue-system with a kernel 4.8.??? to change a
harddisk-config on a server and i get the same problem:
to backup, format and restore a filesystem with less then 1 GB data i need over
2 hours.
the initialisation of a 160GB ext3-filesystem need over 30 minutes. this is
impossible!

at the same time, a raid is rebuild with over 100 MB/s. i stop the rebuild, but
this have no effect to the write-speed of mke2fs to init the filesystem. at
last, i reinstall the system in less then 30 minutes two times again because
the system don't boot after my changes. i think a selinux-problem.
this systenm use kernel 3.10.0 at the moment without problems.

after two days, i install the kernel 3.18.47 from kernel.org to have the latest
3.xx kernel and this kernel works fine and since installation without problems.

only, i must deaktivate initramfs, but i think, that is no problem of the
kernel and i have no time to analyse this problem at the moment.

goodby

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2017-02-08 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 16:05 bugzilla-daemon [this message]
2017-02-08 19:49 ` [Bug 194511] filesystem slow down bugzilla-daemon
2017-02-09 11:20 ` bugzilla-daemon
2017-05-07  8:05 ` bugzilla-daemon
2017-05-07 12:34 ` bugzilla-daemon

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=bug-194511-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.