"Disks" formatted mounted disk ext4->NTFS without unmount, resulting in kernel panic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
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
(This is Linux Mint 15 MATE edition)
lsblk = 'NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 298.1G 0 disk
sdb 8:16 0 465.8G 0 disk
sdc 8:32 0 698.7G 0 disk
│ └─md0 9:0 0 465.7G 0 raid1
sdd 8:48 1 7.9G 0 disk
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 partitions-- the fact the "Disks" was able to format an in-use, mounted partition is very worrying.
description: | updated |
description: | updated |
affects: | gnome-disk-utility (Ubuntu) → linux (Ubuntu) |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1263257
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.