After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609468 - Palimpsest should be able to create JFS partitions
Palimpsest should be able to create JFS partitions
Status: RESOLVED FIXED
Product: gnome-disk-utility
Classification: Core
Component: Disks UI
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2010-02-09 22:45 UTC by Florent Thévenet
Modified: 2012-11-12 21:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Florent Thévenet 2010-02-09 22:45:18 UTC 
Palimpsest can't format a drive as JFS while ubuntu's installer and gparted can.

Read more at the launchpad bug report : https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/519495
Comment 1 Jean-Christophe Berthon 2010-02-28 15:07:47 UTC 
I have tested it again with the latest Ubuntu Lucid Alpha and the bug is still there. Palimpset offers to format in a variety of file system types, however many of the propose choices (like XFS) are not present on the system (thus palimpset cannot format to XFS eventhoug it is proposed), and eventhough the jfs utils are installed, JFS is not part of the choice.
Comment 2 David Zeuthen (not reading bugmail) 2012-11-12 21:31:06 UTC 
FWIW, I don't think it's very important to support a lot of random filesystems - chances are if you know what JFS and XFS means you'd use the command-line anyway - so that's why you see this

 http://people.freedesktop.org/~david/gnome-disks-format-fs-type.png

in Disks 3.7 (it's been like since since Disks 3.4).

Notably, this dialog *does* allow you to select the "Custom" item in the combobox. This will reveal a "Filesystem" text entry box where you can enter 'jfs' (it currently defaults to 'btrfs'). So for some values of FIXED, this is now, uhm, FIXED! Closing as such.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.