| View previous topic :: View next topic |
| Author |
Message |
krotuss
Apprentice
Joined: 01 Aug 2008
Posts: 235
|
 Posted: Thu Oct 17, 2024 6:23 pm Post subject: Could I mess up my btrfs? |
 |
|
Hi,
I have pulled one drive from my desktop and connected it to rpi5 to test performance.
At first I got obscure error:
| Code: |
[ 174.953922] BTRFS warning (device dm-0): v1 space cache is not supported for page size 16384 with sectorsize 4096
[ 174.954154] BTRFS error (device dm-0): open_ctree failed
|
googling returned mostly cases of corrupted fs, and it took me a while to connect those two together. So after some trial and error I had tried with nospace_cache option and succeeded:
| Code: |
BTRFS warning (device dm-0): read-write for sector size 4096 with page size 16384 is experimental
|
Now I am little worried, I have not done any writes to it, but maybe OS did. Wasn't it customary to require some option to enable experimental, and potentially unsafe, features? On top of that, fs now mounts even without nospace_cache option, so something was probably written. I am curious about what happened to that v1 cache Was it erased, or fs just remembers that it is disabled? From this I have not understood that nospace_chache is persistent.
| Code: | | The v1 space cache can be disabled at mount time with nospace_cache without clearing. |
|
|
| Back to top |
|
 |
krotuss
Apprentice
Joined: 01 Aug 2008
Posts: 235
|
| Posted: Sat Oct 19, 2024 8:43 pm Post subject: |
|
|
Warning is also reported when I mount with -oro:
| Code: | BTRFS warning (device dm-0): read-write for sector size 4096 with page size 16384 is experimental
|
What I find confusing is if it means read-write as opposed to read-only, and is therefore superfluous, or that both reading and writing is experimental. |
|
| Back to top |
|
|
krotuss
Apprentice
Joined: 01 Aug 2008
Posts: 235
|
| Posted: Sat Oct 19, 2024 9:08 pm Post subject: |
|
|
I have attempted to run scrub, this is what happened:
| Code: | btrfs scrub start /mnt/drive9/
scrub started on /mnt/drive9/, fsid *redacted* (pid=31540)
Starting scrub on devid 1
btrfs scrub status /mnt/drive9/
UUID: *redacted*
Scrub started: *redacted*
Status: aborted
Duration: 0:00:00
Total to scrub: 3.60TiB
Rate: 0.00B/s
Error summary: no errors found
|
There is nothing in dmesg. Is there a way how can I find out why it was immediately aborted? Maybe it has to be mounted rw, maybe not. The point is that I don't know. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
