AW: zRAM broken on Raring?
PhillW at Ubuntu.com
Thu Oct 3 17:38:51 UTC 2013
I strongly suspect that the the 'sudo parted -l' output of 'Error:
/dev/zram1: unrecognised disk label', has been around for quite some time.
I think it was found when people went digging into the issue with zram
The good news is that that particular error is not seen in the 3.12rc1 and
rc2 kernel that I ran as part of digging into the freeze issue. I'm not
completely sure if ubuntu will be switching to this kernel for the 14.04
LTS. That is a decision for the kernel team.
On 2 October 2013 20:11, John Hupp <lubuntu at prpcompany.com> wrote:
> On 9/29/2013 4:17 AM, Leszek Lesner wrote:
> It can be disabled just like any other upstart service.
> Here is a short documentation link:
> So renaming /etc/init/zram-config.conf to
> /etc/init/zram-config.donotstart should work here.
> Thanks, Leszek, this was the cleanest work-around. Disabling the Upstart
> job means that the zram configurations never run to begin with.
> And it doesn't leave anything dubious dangling (like the 'sudo parted -l'
> output of 'Error: /dev/zram1: unrecognised disk label').
> *Von: *Nio Wiklund
> *Gesendet: *Sonntag, 29. September 2013 10:11
> *An: *Leszek Lesner; John Hupp; lubuntu-users at lists.ubuntu.com
> *Betreff: *Re: AW: zRAM broken on Raring?
> Hi Leszek,
> John has zRAM in Raring. It was pulled in by a package he installed, and
> I try to help him switch it off.
> Probably it is better to do it in /etc/init.d, but I am not familiar
> with that method, so I didn't suggest that method. Please describe it,
> I'm reading and learning :-)
> Best regards
> On 2013-09-29 10:03, Leszek Lesner wrote:
> > Honestlky I don't get the cronjob. Why is it necessary? On reboot the
> > init system runs the stop command on zram-config in /etc/init.d which
> > dies exactly the same as the cronjob here.
> > *Von: *Nio Wiklund
> > *Gesendet: *Sonntag, 29. September 2013 08:29
> > *An: *John Hupp; lubuntu-users at lists.ubuntu.com
> > *Betreff: *Re: zRAM broken on Raring?
> > On 2013-09-29 02:23, John Hupp wrote:
> >> On 9/28/2013 12:23 PM, sudodus wrote:
> >>> Hi John,
> >>> Yes, let us hope the bug will be fixed soon, and it will be
> >>> back-ported :-)
> >>> Can you run your application without zRAM? You can switch it off in a
> >>> simple way (and have it ready for reactivation) like this with crontab.
> >>> Edit the crontab with
> >>> sudo crontab -e
> >>> $ sudo crontab -l |tail -n3
> >>> # m h dom mon dow command
> >>> @reboot /sbin/swapoff /dev/zram*
> >>> @reboot /sbin/rmmod zram
> >>> Best regards
> >>> Nio
> >> I set up a root crontab as you suggested, Nio, and syslog confirms that
> >> the two crontab commands are run after the zram setup commands.
> >> But sudo parted -l still reports:
> >> Error: /dev/zram1: unrecognised disk label
> >> Does anyone know if the zram1 device would be using memory (the setup
> >> command designated 512MB for zram on this 1GB setup) or otherwise doing
> >> any harm?
> > Hi John,
> > The zRAM is not removed, only de-activated. Only if zRAM is used already
> > '@reboot', when cron runs the command, and there is no place to put the
> > content, then swapoff would fail (I think).
> > 1. Did you check with
> > swapon -s
> > This command should return no zram block device.
> > 2. Check the memory with
> > free -m
> > and install and run
> > htop
> > to check if something related to zram is running or using memory.
> > Best regards
> > Nio
> > --
> > Lubuntu-users mailing list
> > Lubuntu-users at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
> Lubuntu-users mailing list
> Lubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Lubuntu-users