Feature requet: Full F2FS support in Ubuntu 15.10
Seeing that Ubuntu 15.10 will ship with version 4.2 of the Linux kernel that will have improvements to the F2FS file system, will there be an effort to update Ubiquity to support it during install? Sa.e goes for the f2fs-package being available during a live CD for gparted as well. If GRUB doesn't support booting from F2FS, maybe add a warning as some of us will have the separate /boot partition formatted to EXT4 while / and /home may be using F2FS. In past releases, we had to add f2fs to /etc/initramfs-tools/modules in order for the OS to load it during boot. If we can remove that requirement, then that would be great too. In summary, it seems about time for F2FS support to be ready for Ubuntu for the 15.10 out of the box as there have been many improvements to it at the kernel level in the 4.x series and the f2fs-tools package has matured as well. Heck, if this works out, maybe consider it for 14.04.4 down the road as it will have the 4.2 kernel as well. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
kGraft/kPatch support in Ubuntu 15.10 or 16.04?
Hello, I was very excited to see live kernel patching get accepted into the mainline kernel in 4.0. For server environments where uptime is crucial and rebooting servers to install kernel security fixes is very disruptive, the ability to live patch security fixes into the running kernel is a very desirable feature. Are there any plans to add support for the kGraft/kPatch support available in 4.x series kernels in Ubuntu Server 15.10 or 16.04? This would be a fantastic feature for the next LTS release! Thanks, Andrew Martin -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: How to file a bug against an unknown package? - Was: Green hard disk drives
On 08/13/2015 10:20 PM, Ralf Mardorf wrote: Write frequency : 4 systemd-journal 10 kworker/u8:2 45 kworker/u8:1 60 kworker/u8:0 128 jbd2/sdb11-8 If jbd2 is writing 12.8 times per min how can your disk spin down after 30 min? Even if you increase jdb2 sync like I did, kworker will continue writing every few seconds, so how can the drive spin-down? I must me missing something. -- João M. S. Silva -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: How to file a bug against an unknown package? - Was: Green hard disk drives
On Sat, 15 Aug 2015 00:57:42 +0100, João M. S. Silva wrote: If jbd2 is writing 12.8 times per min how can your disk spin down after 30 min? As already pointed out, the drive in question is _sdc_, not _sdb_ [1]. Regards, Ralf [1] On Thu, 13 Aug 2015 23:20:25 +0200, Ralf Mardorf wrote: [snip] A script running lm-profiler didn't find anything /dev/sdc related, ^^^ ^^^ while the Start_Stop and Load_Cycle counts increased. [snip] sdc is the external green drive sdb11 is the Ubuntu install including all directories, no separated partitions, excepted of data partitions This is the relevant part of the script's log file: [weremouse@moonstudio ~]$ grep 2015 -A4 -B21 /var/log/lm-profiler08Aug2015_195923.log Thu, 08 Aug 2015 19:59:23 +0200 smartctl -A /dev/sdc|grep Cou|grep -v R [snip] ^^^ ^^^ [snip] 4 systemd-journal 10 kworker/u8:2 45 kworker/u8:1 60 kworker/u8:0 128 jbd2/sdb11-8 [snip] ^^^ ^^^ -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: How to file a bug against an unknown package? - Was: Green hard disk drives
On 08/15/2015 01:12 AM, Ralf Mardorf wrote: As already pointed out, the drive in question is _sdc_, not _sdb_ [1]. What about kworker? -- João M. S. Silva -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: How to file a bug against an unknown package? - Was: Green hard disk drives
On Sat, 15 Aug 2015 01:33:46 +0100, João M. S. Silva wrote: On 08/15/2015 01:12 AM, Ralf Mardorf wrote: As already pointed out, the drive in question is _sdc_, not _sdb_ What about kworker? I wonder, if AppArmor or any of the other software I didn't chose to install myself could be the culprit. It unlikely is kernel related. It most likely is caused by some user space software. However, I anyway need to compile an Rt patched kernel and could do it, using the same config as for my Arch install. [rocketmouse@archlinux ~]$ grep kwork /mnt/moonstudio/var/log/lm-profiler08Aug2015_195923.log | grep sdc [rocketmouse@archlinux ~]$ grep kwork /mnt/moonstudio/var/log/lm-profiler08Aug2015_195923.log Write accesses at 7/600 in lm-profiler run: kworker/u8:0 Write accesses at 30/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 34/600 in lm-profiler run: kworker/u8:0 Write accesses at 39/600 in lm-profiler run: kworker/u8:1 Write accesses at 44/600 in lm-profiler run: kworker/u8:1 Write accesses at 48/600 in lm-profiler run: kworker/u8:1 Write accesses at 57/600 in lm-profiler run: kworker/u8:0 Write accesses at 62/600 in lm-profiler run: kworker/u8:0 Write accesses at 66/600 in lm-profiler run: kworker/u8:1 Write accesses at 71/600 in lm-profiler run: kworker/u8:1 Write accesses at 75/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 systemd-journal Write accesses at 80/600 in lm-profiler run: kworker/u8:0 Write accesses at 85/600 in lm-profiler run: kworker/u8:0 Write accesses at 89/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 94/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 98/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 103/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 107/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 112/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 121/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 126/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 130/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 135/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 139/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 144/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 153/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 158/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 162/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 167/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 176/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 185/600 in lm-profiler run: kworker/u8:0 Write accesses at 190/600 in lm-profiler run: kworker/u8:0 Write accesses at 194/600 in lm-profiler run: kworker/u8:1 Write accesses at 199/600 in lm-profiler run: kworker/u8:1 Write accesses at 203/600 in lm-profiler run: kworker/u8:1 Write accesses at 208/600 in lm-profiler run: kworker/u8:0 Write accesses at 212/600 in lm-profiler run: kworker/u8:0 Write accesses at 217/600 in lm-profiler run: kworker/u8:0 Write accesses at 221/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 226/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 231/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 235/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 240/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 244/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 249/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 258/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 267/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 272/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 276/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 281/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:1 Write accesses at 290/600 in lm-profiler run: jbd2/sdb11-8 kworker/u8:0 Write accesses at 299/600 in lm-profiler run: kworker/u8:0 Write accesses at 304/600 in lm-profiler run: kworker/u8:1 Write accesses at 308/600 in lm-profiler run: kworker/u8:1 Write accesses at 313/600 in lm-profiler run: kworker/u8:1 Write accesses at 317/600 in lm-profiler
