** Description changed: gnome-disk-utility "Disks", version 3.6.1-1ubuntu1 System in question: - uname -a = 'Linux scorpio 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux' - lsb_release -a = 'Distributor ID: LinuxMint - Description: Linux Mint 15 Olivia - Release: 15 - Codename: olivia' - (This is Linux Mint 15 MATE edition) - lsblk = 'NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - sda 8:0 0 298.1G 0 disk - ├─sda1 8:1 0 15.3G 0 part / - ├─sda2 8:2 0 2.8G 0 part [SWAP] - ├─sda3 8:3 0 15.6G 0 part - ├─sda4 8:4 0 7.9M 0 part - └─sda5 8:5 0 264.5G 0 part /home - sdb 8:16 0 465.8G 0 disk - └─sdb1 8:17 0 465.8G 0 part - └─md0 9:0 0 465.7G 0 raid1 - sdc 8:32 0 698.7G 0 disk - ├─sdc1 8:33 0 465.8G 0 part - │ └─md0 9:0 0 465.7G 0 raid1 - └─sdc2 8:34 0 232.9G 0 part /media/ed/Spare - sdd 8:48 1 7.9G 0 disk - └─sdd1 8:49 1 7.9G 0 part /media/ed/MEMSTICK + uname -a = 'Linux scorpio 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux' + lsb_release -a = 'Distributor ID: LinuxMint + Description: Linux Mint 15 Olivia + Release: 15 + Codename: olivia' + (This is Linux Mint 15 MATE edition) + lsblk = 'NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT + sda 8:0 0 298.1G 0 disk + ├─sda1 8:1 0 15.3G 0 part / + ├─sda2 8:2 0 2.8G 0 part [SWAP] + ├─sda3 8:3 0 15.6G 0 part + ├─sda4 8:4 0 7.9M 0 part + └─sda5 8:5 0 264.5G 0 part /home + sdb 8:16 0 465.8G 0 disk + └─sdb1 8:17 0 465.8G 0 part + └─md0 9:0 0 465.7G 0 raid1 + sdc 8:32 0 698.7G 0 disk + ├─sdc1 8:33 0 465.8G 0 part + │ └─md0 9:0 0 465.7G 0 raid1 + └─sdc2 8:34 0 232.9G 0 part /media/ed/Spare + sdd 8:48 1 7.9G 0 disk + └─sdd1 8:49 1 7.9G 0 part /media/ed/MEMSTICK Attempted to format drive in question (/dev/sdc2, /dev/sdb2 before reboot) from ext4 to NTFS, failed to unmount disk beforehand. Admittably a failure in proper user policy; but a frontend graphical program like "Disks" should know better than to have actually tried to preform said operation without doing an unmount first. Result was a partition which read 16EB (exabyte) ext3/ext4 in caja shell properties window. Attempt to unmount via caja shell resulted in kernel panic :( Clearly this is a very serious issue; anybody working on disk partioning - could potentially make this mistake. Shell format utilites would + could potentially make this mistake. Terminal format utilites would actually complain about mounted disks-- the fact the "Disks" was able to format an in-use, mounted drive is very worrying.
** Description changed: gnome-disk-utility "Disks", version 3.6.1-1ubuntu1 System in question: uname -a = 'Linux scorpio 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux' lsb_release -a = 'Distributor ID: LinuxMint Description: Linux Mint 15 Olivia Release: 15 Codename: olivia' (This is Linux Mint 15 MATE edition) lsblk = 'NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 298.1G 0 disk ├─sda1 8:1 0 15.3G 0 part / ├─sda2 8:2 0 2.8G 0 part [SWAP] ├─sda3 8:3 0 15.6G 0 part ├─sda4 8:4 0 7.9M 0 part └─sda5 8:5 0 264.5G 0 part /home sdb 8:16 0 465.8G 0 disk └─sdb1 8:17 0 465.8G 0 part └─md0 9:0 0 465.7G 0 raid1 sdc 8:32 0 698.7G 0 disk ├─sdc1 8:33 0 465.8G 0 part │ └─md0 9:0 0 465.7G 0 raid1 └─sdc2 8:34 0 232.9G 0 part /media/ed/Spare sdd 8:48 1 7.9G 0 disk └─sdd1 8:49 1 7.9G 0 part /media/ed/MEMSTICK - Attempted to format drive in question (/dev/sdc2, /dev/sdb2 before - reboot) from ext4 to NTFS, failed to unmount disk beforehand. Admittably - a failure in proper user policy; but a frontend graphical program like - "Disks" should know better than to have actually tried to preform said - operation without doing an unmount first. Result was a partition which - read 16EB (exabyte) ext3/ext4 in caja shell properties window. Attempt - to unmount via caja shell resulted in kernel panic :( + Attempted to format partition in question (/dev/sdc2, /dev/sdb2 before + reboot) from ext4 to NTFS, failed to unmount partition beforehand. + Admittably a failure in proper user policy; but a frontend graphical + program like "Disks" should know better than to have actually tried to + preform said operation without doing an unmount first. Result was a + partition which read 16EB (exabyte) ext3/ext4 in caja shell properties + window. Attempt to unmount via caja shell resulted in kernel panic :( Clearly this is a very serious issue; anybody working on disk partioning could potentially make this mistake. Terminal format utilites would - actually complain about mounted disks-- the fact the "Disks" was able to - format an in-use, mounted drive is very worrying. + actually complain about mounted partitions-- the fact the "Disks" was + able to format an in-use, mounted partition is very worrying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263257 Title: "Disks" formatted mounted disk ext4->NTFS without unmount, resulting in kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1263257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs