[SOLVED] Running within VirtualBox: btrfs errors when installing a container via CA

[Dan Gravell]

I know - running within VirtualBox isn't supported. Feel free to ignore and I'll get the message.

 

However, I have managed to get as far as playing about with Docker, so I was hoping someone might be able to give me a pointer.

 

Whenever I try to install an app from Community Applications, when the docker pull starts, I eventually get errors like:

 

Mar 17 15:55:43 Tower kernel: print_req_error: 55 callbacks suppressed
Mar 17 15:55:43 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 80064 op 0x1:(WRITE) flags 0x1800 phys_seg 43 prio class 0
Mar 17 15:55:43 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 604352 op 0x1:(WRITE) flags 0x1800 phys_seg 43 prio class 0
Mar 17 15:55:43 Tower kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2377: errno=-5 IO failure (Error while writing out transaction)
Mar 17 15:55:43 Tower kernel: BTRFS info (device loop2): forced readonly
Mar 17 15:55:43 Tower kernel: BTRFS warning (device loop2): Skipping commit of aborted transaction.
Mar 17 15:55:43 Tower kernel: BTRFS: error (device loop2) in cleanup_transaction:1942: errno=-5 IO failure

 

... and the install fails.

 

I don't have a cache AFAIK.

 

I have tried recreating docker.img but that hasn't fixed it.

 

I have tried scrubbing the btrfs volume, but that didn't help.

 

Diagnostics attached... Very grateful for any help.

 

tower-diagnostics-20210317-1605.zip

[JorgeB]

Docker image is on disk1, and disk1 is full:

 

Filesystem      Size  Used Avail Use% Mounted on
/dev/md1        2.0G  2.0G   24K 100% /mnt/disk1

 

[Dan Gravell]

Thanks - I made a stupid assumption that storage was abstracted in the same way lvm would do - I didn't think individual disks mattered.

 

So I recreated the disks, much larger, and it works. Thanks again.