fedora-infrastructure

#7405 backend build storage cannot be mounted
Closed: Fixed Opened by clime.

Closed: Fixed
Reopen Issue
  • Describe what you need us to do:
    Could you, please, look at the copr-be-data volume (UUID acb52b07-12cd-47fb-ab35-75205c6472be) and try to fix it so that it can be mounted again to /var/lib/copr/public_html?

Here is a tail of dmesg:

[3383117.652297] print_req_error: I/O error, dev vdc, sector 4269804040
[3383117.655864] EXT4-fs error (device vdc1): __ext4_get_inode_loc:4630: inode #66716543: block 533725271: comm ls: unable to read itable block
[3383117.661498] Buffer I/O error on dev vdc1, logical block 0, lost sync page write
[3383117.663856] EXT4-fs (vdc1): I/O error while writing superblock
[3383117.668500] EXT4-fs error (device vdc1): __ext4_get_inode_loc:4630: inode #46598478: block 372768948: comm ls: unable to read itable block
[3383117.673593] Buffer I/O error on dev vdc1, logical block 0, lost sync page write
[3383117.675907] EXT4-fs (vdc1): I/O error while writing superblock
[3383117.679296] EXT4-fs error (device vdc1): __ext4_get_inode_loc:4630: inode #71697046: block 573571145: comm ls: unable to read itable block
[3383117.683973] Buffer I/O error on dev vdc1, logical block 0, lost sync page write
[3383117.686202] EXT4-fs (vdc1): I/O error while writing superblock
[3383117.688792] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.693410] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.698329] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.703367] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.708418] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.713319] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.718565] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.723996] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383117.729785] EXT4-fs warning (device vdc1): htree_dirblock_to_tree:978: inode #46596097: lblock 4: comm ls: error -5 reading directory block
[3383222.890701] print_req_error: 5875 callbacks suppressed
[3383222.890703] print_req_error: I/O error, dev vdc, sector 2048
[3383222.900909] print_req_error: I/O error, dev vdc, sector 2048
[3383222.903337] Buffer I/O error on dev vdc1, logical block 0, lost sync page write
[3383222.906106] EXT4-fs (vdc1): I/O error while writing superblock
[3383222.908636] EXT4-fs error (device vdc1): ext4_remount:5167: Abort forced by user
[3383700.828048] print_req_error: I/O error, dev vdc, sector 2050
[3383700.834266] EXT4-fs (vdc1): unable to read superblock

This occurred before and it was a problem with cloud storage reaching threshold of acceptable storage size. Now we have it again.

  • When do you need this? (YYYY/MM/DD)
    today would be good

  • When is this no longer needed or useful? (YYYY/MM/DD)
    always useful

  • If we cannot complete your request, what is the impact?
    Copr won't be operable.

This was fixed by @puiterwijk the other night. Basically the volume grew some more and ran out of space. ;(

We really should delete unneeded snapshots from there so there's more free space.

In the mean time things should all be back to normal.

:minidisc:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.