linux question/problem

Dan__ · 08-29-2021, 12:29 AM

Hello,
I have a computer with a small hard drive and I have many GB's of books so, when I was running Windows, I put the calibre database on a windows share of another machine. Calibre worked with zero problems.

I recently switched to linux and installed calibre 5.26.

On linux the database is a permanently mounted cifs volume. All other non-calibre files on that volume are accessible with no problems.

When I try to tell calibre to use that same database that I was using with Windows, I get a bunch of python messages from initialize_db, create_backend, etc. concluding with a apsw.BusyError: BudyError: database is locked.

I don't understand this. I am the only user. I have only one machine that connects to this database and it was closed cleanly on Windows before the switch to linux.

I would love to understand what is going on here.

Any help would be greatly appreciated.

kovidgoyal · 08-29-2021, 12:30 AM

Network filesystems are broken, you will get random errors/data loss. Dont use them. https://manual.calibre-ebook.com/faq...rked-drive-nas

Dan__ · 08-29-2021, 12:56 AM

only broken in linux?

kovidgoyal · 08-29-2021, 12:58 AM

Nope, broken everywhere, you just got lucky in windows, your luck could have turned at any moment.

Though I should note that Linux in general has the most buggy filesystems, probably because it has so many, and most of them are very poorly implemented.

Dan__ · 08-29-2021, 01:08 AM

Thanks

theducks · 08-29-2021, 04:26 PM

Is the HD in your computer Replaceable?
I cloned my Laptops HD onto a 1T SSD for under $100.

Clonezilla will clone a dual boot drive that neither of WD or Maxtor tools would.

All you need is a USB caddy or a HD clone cable (does IDE or SATA).

Dan__ · 08-29-2021, 05:29 PM

Quote:

Originally Posted by theducks

Is the HD in your computer Replaceable?
I cloned my Laptops HD onto a 1T SSD for under $100.

Clonezilla will clone a dual boot drive that neither of WD or Maxtor tools would.

All you need is a USB caddy or a HD clone cable (does IDE or SATA).

I don't thing it will solve this problem but yes, my system disk is already an SSD in a hot-swap bay and I clone it regularly.

Thanks

theducks · 08-29-2021, 07:57 PM

Quote:

Originally Posted by Dan__

I don't thing it will solve this problem but yes, my system disk is already an SSD in a hot-swap bay and I clone it regularly.

Thanks

I was trying to cure the 'too small HD' problem. SSD was just to point out how inexpensive bigger has gotten, but also get a faster option.
You done that already --Kingston Trio

Dan__ · 08-30-2021, 12:22 AM

As far as space I have 2 raid 5 units, 12 & 16 TB. I think I’m set for the next week or two

Dan__ · 08-31-2021, 07:35 PM

Hi again,
I'm on linux with a calibre database in my home directory. I just booted the machine and tried to run "calibredb list" and got - after a very long pause -

Traceback (most recent call last):
File "runpy.py", line 194, in _run_module_as_main
File "runpy.py", line 87, in _run_code
File "site.py", line 45, in <module>
File "site.py", line 41, in main
File "calibre/db/cli/main.py", line 251, in main
File "calibre/db/cli/main.py", line 41, in run_cmd
File "calibre/db/cli/cmd_list.py", line 315, in main
File "calibre/db/cli/cmd_list.py", line 148, in do_list
File "calibre/db/cli/main.py", line 184, in run
File "calibre/db/cli/main.py", line 171, in db
File "calibre/db/legacy.py", line 188, in __init__
File "calibre/db/legacy.py", line 45, in create_backend
File "calibre/db/backend.py", line 470, in __init__
File "calibre/db/schema_upgrades.py", line 19, in __init__
File "calibre/db/backend.py", line 937, in execute
apsw.BusyError: BusyError: database is locked

AFIK there is NO networking involved in accessing my local db on my local machine. Nevertheless, this error message is almost identical to to one I got when my db was in dropbox (my initial question).

I'm sorry, but I'm now totally confused. I was prepared to accept your explanation that networking was the culprit but since the problem also occurs with no networking, it makes me wonder if there isn't something else going on.

kovidgoyal · 08-31-2021, 09:19 PM

The only way you can get a database busy error is

1) on a broken filesystem

2) if something else is accessing the database. So what else do you have accessing the database

Dan__ · 08-31-2021, 10:16 PM

Nothing that I know of. I'll reboot again and try once more. Maybe it will have healed itself

08-29-2021, 12:29 AM	#1
Dan__ Zealot Posts: 110 Karma: 10 Join Date: Feb 2011 Device: Nook - Simple Touch	linux question/problem Hello, I have a computer with a small hard drive and I have many GB's of books so, when I was running Windows, I put the calibre database on a windows share of another machine. Calibre worked with zero problems. I recently switched to linux and installed calibre 5.26. On linux the database is a permanently mounted cifs volume. All other non-calibre files on that volume are accessible with no problems. When I try to tell calibre to use that same database that I was using with Windows, I get a bunch of python messages from initialize_db, create_backend, etc. concluding with a apsw.BusyError: BudyError: database is locked. I don't understand this. I am the only user. I have only one machine that connects to this database and it was closed cleanly on Windows before the switch to linux. I would love to understand what is going on here. Any help would be greatly appreciated.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Linux/Calibre client question	james_	Calibre	4	04-15-2021 07:09 PM
Font problem (Linux).	Giorgos	Conversion	2	08-14-2017 11:48 AM
Calibre GUI linux question	ziprar	Calibre	0	03-19-2012 05:40 AM
Linux installer question	opitzs	Calibre	2	11-09-2011 07:20 AM
[Old Thread] Linux Question: Library/DB/Server Only?	zenrhino	Calibre	15	03-31-2011 12:32 PM

08-29-2021, 12:30 AM	#2
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Network filesystems are broken, you will get random errors/data loss. Dont use them. https://manual.calibre-ebook.com/faq...rked-drive-nas

08-29-2021, 12:56 AM	#3
Dan__ Zealot Posts: 110 Karma: 10 Join Date: Feb 2011 Device: Nook - Simple Touch	only broken in linux?

08-29-2021, 12:58 AM	#4
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Nope, broken everywhere, you just got lucky in windows, your luck could have turned at any moment. Though I should note that Linux in general has the most buggy filesystems, probably because it has so many, and most of them are very poorly implemented.

08-29-2021, 01:08 AM	#5
Dan__ Zealot Posts: 110 Karma: 10 Join Date: Feb 2011 Device: Nook - Simple Touch	Thanks

08-29-2021, 04:26 PM	#6
theducks Well trained by Cats Posts: 31,251 Karma: 61360164 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	Is the HD in your computer Replaceable? I cloned my Laptops HD onto a 1T SSD for under $100. Clonezilla will clone a dual boot drive that neither of WD or Maxtor tools would. All you need is a USB caddy or a HD clone cable (does IDE or SATA).

08-30-2021, 12:22 AM	#9
Dan__ Zealot Posts: 110 Karma: 10 Join Date: Feb 2011 Device: Nook - Simple Touch	As far as space I have 2 raid 5 units, 12 & 16 TB. I think I’m set for the next week or two

08-31-2021, 07:35 PM	#10
Dan__ Zealot Posts: 110 Karma: 10 Join Date: Feb 2011 Device: Nook - Simple Touch	Hi again, I'm on linux with a calibre database in my home directory. I just booted the machine and tried to run "calibredb list" and got - after a very long pause - Traceback (most recent call last): File "runpy.py", line 194, in _run_module_as_main File "runpy.py", line 87, in _run_code File "site.py", line 45, in <module> File "site.py", line 41, in main File "calibre/db/cli/main.py", line 251, in main File "calibre/db/cli/main.py", line 41, in run_cmd File "calibre/db/cli/cmd_list.py", line 315, in main File "calibre/db/cli/cmd_list.py", line 148, in do_list File "calibre/db/cli/main.py", line 184, in run File "calibre/db/cli/main.py", line 171, in db File "calibre/db/legacy.py", line 188, in __init__ File "calibre/db/legacy.py", line 45, in create_backend File "calibre/db/backend.py", line 470, in __init__ File "calibre/db/schema_upgrades.py", line 19, in __init__ File "calibre/db/backend.py", line 937, in execute apsw.BusyError: BusyError: database is locked AFIK there is NO networking involved in accessing my local db on my local machine. Nevertheless, this error message is almost identical to to one I got when my db was in dropbox (my initial question). I'm sorry, but I'm now totally confused. I was prepared to accept your explanation that networking was the culprit but since the problem also occurs with no networking, it makes me wonder if there isn't something else going on.

08-31-2021, 09:19 PM	#11
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The only way you can get a database busy error is 1) on a broken filesystem 2) if something else is accessing the database. So what else do you have accessing the database

08-31-2021, 10:16 PM	#12
Dan__ Zealot Posts: 110 Karma: 10 Join Date: Feb 2011 Device: Nook - Simple Touch	Nothing that I know of. I'll reboot again and try once more. Maybe it will have healed itself