[Bug 1078552] New: Filesystems shown as TODO - prevents mounting existing filesystems
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552 Bug ID: 1078552 Summary: Filesystems shown as TODO - prevents mounting existing filesystems Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: per@computer.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- In the expert partitioner, the file systems are displayed as TODO. When I tried to mount a previously formatted volume, it wouldn't let me. For testing that's okay, but otherwise it's a show-stopper. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c3
--- Comment #3 from Per Jessen
file systems as TODO is already reported. But mounting previously formatted volume should work.
Sorry, it wasn't the 'FS type' column, it is called just 'Type'. The option to mount can't be selected. This is a JFS volume - with e.g. ext4, it works. Oh, I see, it isn't even recognised as a JFS volume. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c4
--- Comment #4 from Per Jessen
TODO labels were replaced by correct data in version 4.0.73 of package yast2-storage-ng. What version is used in your build image?
Whatever was in the repo - I presume: yast2-storage-ng-4.0.76-lp150.1.1.noarch.rpm -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c5
--- Comment #5 from Per Jessen
(In reply to José Iván López González from comment #2)
TODO labels were replaced by correct data in version 4.0.73 of package yast2-storage-ng. What version is used in your build image?
Whatever was in the repo -
I presume: yast2-storage-ng-4.0.76-lp150.1.1.noarch.rpm
Looks like this was only just pushed out to the mirrors in the last hour or so. I am just now running a new installatrion, the TODO is gone. I still can't mount the volume with a JFS filesystem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c6
--- Comment #6 from Ancor Gonzalez Sosa
The option to mount can't be selected. This is a JFS volume - with e.g. ext4, it works. Oh, I see, it isn't even recognised as a JFS volume.
JFS support is being dropped. That's intentional. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c7
--- Comment #7 from Per Jessen
(In reply to Per Jessen from comment #3)
The option to mount can't be selected. This is a JFS volume - with e.g. ext4, it works. Oh, I see, it isn't even recognised as a JFS volume.
JFS support is being dropped. That's intentional.
How do we mount existing filesystems then? I guess it's not important to you, but for us that is a complete show-stopper. Would upgrades work? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c8
Anton Aylward
(In reply to Per Jessen from comment #3)
The option to mount can't be selected. This is a JFS volume - with e.g. ext4, it works. Oh, I see, it isn't even recognised as a JFS volume.
JFS support is being dropped. That's intentional.
Is that because support for JFS upstream has been dropped? But ... Let me get this right. You're dropping support for JFS and for ReiserFS. They are both B-tree file systems that support dynamic allocation, rather than the fixed-at-mkfs-time of Ext4. That fixed-at-mkfs-time attitude dates back to the 1960s/1970s and the original UNIX simple & limited kernel code space attitudes. The professional/commercial systems such as AIX etc aren't stuck in this antediluvian attitudes. AIX is where JFS originated. Will that last remaining "other" FS that uses dynamic allocation, XFS, be depreciated as well, forcing us to use BtrFS -- the "one file system to rule all disks" FS -- if there is any uncertainty about the way storage will be used? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
Dave Plater
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c12
--- Comment #12 from Per Jessen
JFS drop is old feature number 2105 ( sorry private only as it is really ancient ).
Quoting from it (not all info is up to date, consider that it is 11 years old, so it is dropped for long time):
Mounting and installing on JFS file systems has been working up until 42.3, no problems.
JFS has more issues and the support from IBM is not as good.
I submit there are no current issues with JFS and developer support is excellent. I ran into a minor fstrim issue only a week ago and had a patch within 70minutes.
Note that SUSE Linux 9.3 already does not support JFS in YaST and mentions this in the release notes.
Like I said, mounting and installing JFS file systems has been working up until 42.3, no problems whatsoever. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552
http://bugzilla.opensuse.org/show_bug.cgi?id=1078552#c13
Josef Reidinger
participants (1)
-
bugzilla_noreply＠novell.com