Downloads go to /tmp on LVM/LUKS disk configuration #4711

New issue

Closed

opened 2026-02-21 17:27:51 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 17:27:51 -05:00

Owner

Originally created by @forabi on GitHub (Sep 15, 2016).

I have Arch Linux configured to use LVM on LUKS. I have set my downloads to be saved in /media/movies which is the mount point of one my logical volumes. Instead of saving to this path, all torrents are being saved to a random directory in /tmp, which means whenever I restart my PC, I lose all downloaded torrents.

qBittorrent v3.3.6
Qt 5.7.0
Libtorrent 1.1.0.0
Boost 1.60.0
Linux 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016 x86_64 GNU/Linux

Originally created by @forabi on GitHub (Sep 15, 2016). I have Arch Linux configured to use LVM on LUKS. I have set my downloads to be saved in `/media/movies` which is the mount point of one my logical volumes. Instead of saving to this path, all torrents are being saved to a random directory in `/tmp`, which means whenever I restart my PC, I lose all downloaded torrents. qBittorrent v3.3.6 Qt 5.7.0 Libtorrent 1.1.0.0 Boost 1.60.0 Linux 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016 x86_64 GNU/Linux

deekerman

2026-02-21 17:27:51 -05:00

closed this issue
added the
OS: Linux

Not an issue
labels

deekerman commented

2026-02-21 17:27:56 -05:00

Author

Owner

@zeule commented on GitHub (Jan 11, 2017):

qBt just passes save path to libtorrent. Looks like a libtorrent issue...

@zeule commented on GitHub (Jan 11, 2017): qBt just passes save path to libtorrent. Looks like a libtorrent issue...

deekerman commented

2026-02-21 17:27:56 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Jan 12, 2017):

Can you share a bit more information about the LUKS/LVM setup you use, so I can test it? Thank you.

@Balls0fSteel commented on GitHub (Jan 12, 2017): Can you share a bit more information about the LUKS/LVM setup you use, so I can test it? Thank you.

deekerman commented

2026-02-21 17:27:56 -05:00

Author

Owner

@forabi commented on GitHub (Jan 12, 2017):

Looks like it does not have anything to do with the LUKS/LVM setup. I have
another machine with standard partitions and I have experienced the same
issue on it. Anyway I haven't had the issue recently, maybe it was fixed in
libtorrent?

Duke notifications@github.com schrieb am Do., 12. Jan. 2017, 10:22 vorm.:

Can you share a bit more information about the LUKS/LVM setup you use, so
I can test it? Thank you.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/qbittorrent/qBittorrent/issues/5742#issuecomment-272102217,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA90GTclvPQaLGK40q_49IBvyYlKOD1Rks5rReLWgaJpZM4J-Pc3
.

@forabi commented on GitHub (Jan 12, 2017): Looks like it does not have anything to do with the LUKS/LVM setup. I have another machine with standard partitions and I have experienced the same issue on it. Anyway I haven't had the issue recently, maybe it was fixed in libtorrent? Duke <notifications@github.com> schrieb am Do., 12. Jan. 2017, 10:22 vorm.: > Can you share a bit more information about the LUKS/LVM setup you use, so > I can test it? Thank you. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/qbittorrent/qBittorrent/issues/5742#issuecomment-272102217>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AA90GTclvPQaLGK40q_49IBvyYlKOD1Rks5rReLWgaJpZM4J-Pc3> > . >

deekerman commented

2026-02-21 17:27:56 -05:00

Author

Owner

@zeule commented on GitHub (Jan 12, 2017):

Thanks for the feedback! Reopen if the problem returns, please.

@zeule commented on GitHub (Jan 12, 2017): Thanks for the feedback! Reopen if the problem returns, please.

deekerman commented

2026-02-21 17:27:56 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Jan 12, 2017):

@forabi Probably, we will never know. It can also be the kernel, or any other userland application.
The most important when it comes to hunting bugs is finding the steps to reproduce the issue. :)

@Balls0fSteel commented on GitHub (Jan 12, 2017): @forabi Probably, we will never know. It can also be the kernel, or any other userland application. The most important when it comes to hunting bugs is finding the steps to reproduce the issue. :)