corrupt disk on app?

1 
2024-04-02T12:25:46.616 app[4d89d921fe3028] ord [info] [ 3835.658671] EXT4-fs error (device vda): __ext4_find_entry:1663: inode #32769: comm ash: reading directory lblock 0
2024-04-02T12:25:48.425 app[4d89d921fe3028] ord [info] [ 3837.467625] blk_update_request: I/O error, dev vda, sector 74136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
2024-04-02T12:25:48.426 app[4d89d921fe3028] ord [info] [ 3837.468916] EXT4-fs error (device vda): __ext4_find_entry:1663: inode #32769: comm ash: reading directory lblock 0
2024-04-02T12:25:51.746 app[4d89d921fe3028] ord [info] [ 3840.788482] blk_update_request: I/O error, dev vda, sector 74136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
2024-04-02T12:25:51.747 app[4d89d921fe3028] ord [info] [ 3840.789500] EXT4-fs error (device vda): __ext4_find_entry:1663: inode #32769: comm ash: reading directory lblock 0
2024-04-02T12:25:56.821 app[4d89d921fe3028] ord [info] [ 3845.862998] blk_update_request: I/O error, dev vda, sector 74136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
2024-04-02T12:25:56.822 app[4d89d921fe3028] ord [info] [ 3845.864491] EXT4-fs error (device vda): __ext4_find_entry:1663: inode #32769: comm ash: reading directory lblock 0

Seems like the disk got corrupted somehow and redeploying my app didn’t help, I had to ssh to it and force reboot it to get it to work again.
Feel like that shouldn’t happen…

2 Likes
2

I just faced a similar error. Tehe solution was a restart for me as well.

I agree this should not happen. And if it does, fly should restart the server automatically.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.