Comment 53 for bug 1217189

Damian, the "fdisk /dev/ram0" was a typo, because I was NOT in any condition to do "copy/paste" from the system, undergoing the zram0 issue. My actual number is different : 314224, but my "situation" is the same, because the number in the "Buffer I/O Error message" was 314223.

Everyone,

This is NOT just a "asthetic" issue under Ubuntu 12.0.4 LTS as, when I examined my RAM situation, while "fdisk /dev/zram0" gave me "number of sectors", I have less RAM, causing a Significant performance degregation, and MUCH thrashing, as my system over-used the poor "Type 82 SWAP Partition" on the same hard drive as all the other files.

PLEASE re-open this, as an ACTUAL problem, not a duplicate, as I see the "steam roller" effect on issue #1215513, where they appear set to "close" that problem as "fixed, but with an 'ugly' message". If any of the technicions (spelling?) are also on that other issue, PLEASE pass along that ONLY fixing the freeze can adversely affect system performance, at least on some of the Ubuntu Releases.

I though the LTS [12.0.4] release was supposed to be "stable". Like I said in a prior message, I'm "supposed" to be a "big picture manager" who just happens to administer a "semi-production" system. I "happily jump" into "detailed debug" mode, when needed, but am "spread thin".

When I was doing things like you do, the "state of the art" release was Red Hat 6! :-O

Now that I've "dated myself" [premature Senior Citizen], I sincerely hope this issue gets the "fantastic customer support" I used to get, when I could phone the developers and "brainstorm" solutions. I met Linus Torvalds at a San Francisco Linux conference once, but don't remember the year. He was very gracious back then. I hope you all still maintain social skills.

Thank you and best regards,

Kenneth Parker, Seattle, WA

-- I'm a troubleshooter. I look for trouble, and shoot it!