[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

[Avamander]

I'm still encountering this once a month or so. It's really awful.

How do I make sure that the kernel **always** has enough memory for
buffers and drivers?

It is absolutely inane that a chrome tab can ever cause filesystem
corruption.

** Also affects: linux
   Importance: Undecided
   Status: New

** Project changed: linux => cryptsetup

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868189

Title:
  Low memory situations result in root partition being remounted read-
  only

To manage notifications about this bug go to:
https://bugs.launchpad.net/cryptsetup/+bug/1868189/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

[Avamander]

Last occurance happened with 5.4.0-29-generic on Ubuntu 20.04 LTS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868189

Title:
  Low memory situations result in root partition being remounted read-
  only

To manage notifications about this bug go to:
https://bugs.launchpad.net/cryptsetup/+bug/1868189/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

[Avamander]

** Description changed:

  Instead of killing something with a high niceness low memory situations
  seem to hang something super-ultra-so-very vital, writes fail and the
  root partition is remounted read-only. After that systemd-journald
  starts stupidly spamming and earlier logs are rendered unusable.
  
  I'd post more logs but https://github.com/systemd/systemd/issues/2339
  hasn't been fixed in years.
  
  This has happened at least four times, across many kernel versions. With
  Ubuntu 18.10, 19.04 and 19.10.
- 
  
  ```
  [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 
00 10 00
  [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 
0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
  [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871518)
  [827788.409154] Buffer I/O error on device dm-1, logical block 3871518
  [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871519)
  [827788.409164] Buffer I/O error on device dm-1, logical block 3871519
  [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 
00 08 00
  [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871598)
  [827788.409180] Buffer I/O error on device dm-1, logical block 3871598
  [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 
00 38 00
  [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 
0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0
  [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871564)
  [827788.409195] Buffer I/O error on device dm-1, logical block 3871564
  [827788.409196] Buffer I/O error on device dm-1, logical block 3871565
  [827788.409198] Buffer I/O error on device dm-1, logical block 3871566
  [827788.409199] Buffer I/O error on device dm-1, logical block 3871567
  [827788.409201] Buffer I/O error on device dm-1, logical block 3871568
  [827788.409202] Buffer I/O error on device dm-1, logical block 3871569
  [827788.409203] Buffer I/O error on device dm-1, logical block 3871570
  [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 
00 08 00
  [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871558)
  [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 
00 08 00
  [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871562)
  [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 
00 08 00
  [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871601)
  [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 
00 30 00
  [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 
0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
  [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827818.628351] sd 5:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 01 93 2f b0 00 
00 08 00
  [827818.628353] blk_update_request: I/O error, dev sdb, sector 26423216 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827818.628358] Aborting journal on device dm-1-8.
  [827818.628374] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 

[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

[Avamander]

I can't run this command because permanent logging stops and temporary
logging is flooded by systemd.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868189

Title:
  Low memory situations result in root partition being remounted read-
  only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868189/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

[Avamander]

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868189

Title:
  Low memory situations result in root partition being remounted read-
  only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868189/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1868189/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868189

Title:
  Low memory situations result in root partition being remounted read-
  only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1868189/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs