reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 208719] PROBLEM: IO lockup on reiserfs FS.
Date: Wed, 29 Jul 2020 02:20:34 +0000	[thread overview]
Message-ID: <bug-208719-695-ZxMBe9Zpf1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208719-695@https.bugzilla.kernel.org/>

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

--- Comment #4 from deference@null.net ---
On the suggestion to not use reiserfs:

My interest in using reiserfs was so that I would have tail packing. I've
searched online and can't find another FS with this function for Linux.
The reason I need tail packing is because I keep a bunch of mostly git
repositories on my system. These contain a lot of files that are either small
or are empty. I could try to hardlink all the empty files and small duplicate
files, but git would complain. I could compress the source code like I do with
normal code bases, but then I'd need to decompress and update them all.
Writing a script to do that would be nothing, it's just the time involved
compressing/decompressing that would be a waist (which is saying nothing
compared to git's love for full histories instead of up-to-the-last-4-versions
or something).

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

  parent reply	other threads:[~2020-07-29  2:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-208719-695@https.bugzilla.kernel.org/>
2020-07-28 15:53 ` [Bug 208719] PROBLEM: IO lockup on reiserfs RAID50 array bugzilla-daemon
2020-07-29  1:59 ` bugzilla-daemon
2020-07-29  1:59 ` [Bug 208719] PROBLEM: IO lockup on reiserfs FS bugzilla-daemon
2020-07-29  2:20 ` bugzilla-daemon [this message]
2020-07-29  2:34 ` bugzilla-daemon
2020-08-17 14:55 ` 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-208719-695-ZxMBe9Zpf1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=reiserfs-devel@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).