I can reproduce this. But nothing to do with udisks, I get the same behaviour if I kill udisks-daemon, chmod it to 0, log out of the desktop session (so no gvfs etc. either), and just run "sudo pm-suspend" on a terminal. Then my mounted USB stick as well as my internal /dev/sda1 (which carries my root partition) get an extra "commit=600" in /proc/mounts. In /etc/fstab / mount output, sdb1 (USB stick) additionally gets "commit=0". In dmesg I see
This does not happen if I use a raw "echo mem | sudo tee /sys/power/state". Then sdb1 just gets unmounted and not re-mounted at all.
The "commit" mount option comes from /usr/lib/pm-utils/power.d/journal-commit.
So the root of the bug is that calling "mount -o remount,commit=600 /dev/sdb1" always appends the new option to /etc/mtab instead of recognizing an already existing one. This doesn't happen in /proc/mounts, so the kernel side is fine.
I can reproduce this. But nothing to do with udisks, I get the same behaviour if I kill udisks-daemon, chmod it to 0, log out of the desktop session (so no gvfs etc. either), and just run "sudo pm-suspend" on a terminal. Then my mounted USB stick as well as my internal /dev/sda1 (which carries my root partition) get an extra "commit=600" in /proc/mounts. In /etc/fstab / mount output, sdb1 (USB stick) additionally gets "commit=0". In dmesg I see
EXT4-fs (sda1): re-mounted. Opts: errors= remount- ro,commit= 600
EXT4-fs (sdb1): re-mounted. Opts: commit=600
This does not happen if I use a raw "echo mem | sudo tee /sys/power/state". Then sdb1 just gets unmounted and not re-mounted at all.
The "commit" mount option comes from /usr/lib/ pm-utils/ power.d/ journal- commit.
So the root of the bug is that calling "mount -o remount,commit=600 /dev/sdb1" always appends the new option to /etc/mtab instead of recognizing an already existing one. This doesn't happen in /proc/mounts, so the kernel side is fine.