public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lee <ny6p01@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] qbittorrent crashes after to many files open error
Date: Thu, 8 Sep 2022 13:26:32 -0700	[thread overview]
Message-ID: <CABpw4G8hKbPg-qPhDCxoUzmAbC0V6QsjiKa+qrL2ugBtt2LHEA@mail.gmail.com> (raw)
In-Reply-To: <d7586cf9-ecf4-1853-1ae5-4e251b791331@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]

Divine punishment perhaps?

Lee 😎

On Wed, Sep 7, 2022, 10:26 PM Dale <rdalek1967@gmail.com> wrote:

> Howdy,
>
> As some know, I discovered torrentting a while back.  It has caused
> issues ever since.  LOL  I recently upgraded qbittorrent.  Other than
> having to limit some speed settings since it would make my desktop
> response slow, it has worked OK, better than ktorrent at least.  Then a
> couple days ago, perhaps related to a upgrade, it would crash.  In the
> notifications I would find a error like below.  I have changed the names
> to protect the innocent.  ;-)
>
> An I/O error occurred for torrent 'ABCDEF'.
> Reason: ABCDEF file_open (/home/dale/Desktop/Videos/ABCDEF error: Too
> many open files
>
>
> I did a google search and found out more info which lead me to this
> eventually:
>
>
> https://www.tecmint.com/increase-set-open-file-limits-in-linux/
>
> Then this:
>
> root@fireball / # sysctl fs.file-max
> fs.file-max = 3289952
> root@fireball / # sysctl -w fs.file-max=32899520
> fs.file-max = 32899520
> root@fireball / # cat /proc/sys/fs/file-max
> 32899520
>
>
> So, I increased the limit on open files by a factor of ten, I added a
> zero on the end.  It was easy enough and didn't require a calculator or
> other fancy maths.  Question is, is this a better fix or could it just
> be qbittorrent itself having issues?  Could there be more to this or
> something else causing this error?
>
> I was using qbittorrent-4.4.5 but downgraded to qbittorrent-4.4.4.  I'm
> hoping one or the other will fix this crashing issue.  It did only start
> after the upgrade but could be a coincidence to I guess.
>
>
> By the way, the 10TB drive I bought a couple weeks or so ago, well, this
> is it now.
>
> /dev/mapper/10tb           9.1T  8.7T  345G  97% /mnt/10tb
>
>
> The 14TB is supposed to be here this weekend.  I have really got to
> create a solution to this.  My current plan, make the 14TB my backup
> drive.  Put the 10TB in my rig, for now.  It's getting full too.  ROFL
> I could cut off the internet I guess.  ROFLMBO
>
>
> Thoughts on the files open error?  Qbittorrent crashing?  Anyone else
> ran into this before?  Proper solution?  Better solution?
>
>
> Dale
>
> :-)  :-)
>
>
>

[-- Attachment #2: Type: text/html, Size: 2931 bytes --]

      parent reply	other threads:[~2022-09-08 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  5:26 [gentoo-user] qbittorrent crashes after to many files open error Dale
2022-09-08 17:19 ` Mateusz Okulus
2022-09-08 22:24   ` Dale
2022-09-08 23:17     ` mad.scientist.at.large
2022-09-12  6:01       ` Dale
2022-09-09 14:23     ` Mateusz Okulus
2022-09-12  6:09       ` Dale
2022-09-08 20:26 ` Lee [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=CABpw4G8hKbPg-qPhDCxoUzmAbC0V6QsjiKa+qrL2ugBtt2LHEA@mail.gmail.com \
    --to=ny6p01@gmail.com \
    --cc=gentoo-user@lists.gentoo.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