Bug 1132651

I reformatted the root filesystems with ext4 and made YaST do a "refresh", didn't change anything. Do I need to go back to the partitioner?

I went back through the partitioner, but that's a bit of a hassle having to go through everything again.

Just one comment - why is this even a show stopper?  Leave it to me to know if I have enough space or not?

Hi Per!

I really appreciate your collaboration reporting us as many bugs as you can find :) Thank you so much!. However, in order to could debug it in a more efficient way, please remember to 

  * Shortly describe what you were trying to do (steps)
  * Indicate what did you expect
  * Tell us what happens instead
  * Attach the logs collected by `save_y2logs`

Thanks!

JFS support is very limited. It might still be possible to mount such a filesystem (didn't test), but for installation we really need a filesystem that we fully support.

As the subject (and unfortunately, ONLY the subject; no reference to that in the bug description at all) says, we can't even check the free space on that filesystem type, so we can't install on that.

(In reply to Stefan Hundhammer from comment #5)
> JFS support is very limited. It might still be possible to mount such a
> filesystem (didn't test), but for installation we really need a filesystem
> that we fully support.

This is clearly a regression wrt Leap15.0 - I don't know if that matters.
Might it be reasonable to just skip the size check on filesystems that are pre-formatted?

(in reply to David Diaz, comment#4)
> I really appreciate your collaboration reporting us as many bugs as you 
> can find :) Thank you so much!. However, in order to could debug it in 
> a more efficient way, please remember to 
>
>  * Shortly describe what you were trying to do (steps)
>  * Indicate what did you expect
>  * Tell us what happens instead
>  * Attach the logs collected by `save_y2logs`

I've doing this for maybe 12-13 years, sometimes I'm a little too fast and I make assumptions :-)
I'll be happy to attach y2logs, if needed.

(In reply to Per Jessen from comment #6)
> I'll be happy to attach y2logs, if needed.
That would be nice. :-) Thanks !

(In reply to Per Jessen from comment #0)
> sda1 has a jfs filesystem.  I thought installing on pre-formatted file
> systems was still supported.

Well, maybe by mistake or "best effort". JFS is not supported at all.

This https://github.com/yast/yast-storage/commit/2effa6b82d8c02a85319e331d766144b4c7e07ba is from 2011

Also mentioned in bugreport https://bugzilla.suse.com/show_bug.cgi?id=869091 (pretty closed one though) and https://bugzilla.novell.com/show_bug.cgi?id=720483 but anyway, JFS is considered to be as dead as JFS can be.

(In reply to Lukas Ocilka from comment #8)
> (In reply to Per Jessen from comment #0)
> > sda1 has a jfs filesystem.  I thought installing on pre-formatted file
> > systems was still supported.
> 
> Well, maybe by mistake or "best effort". JFS is not supported at all.
> 

I'm in no way suggesting we should support JFS, only that we should not actively prevent users from installing on JFS (or any other fs of their choice), that's all.  It works in 15.0. 

I seem to recall you and I having a similar discussion with 15.0?  Yes, see bug#1078552.

Created attachment 803522 [details]
y2logs as saved by save_y2logs

sorry it took a little too long.

Thanks for the logs. From the logs:

2019-04-16 13:53:10 <1> gaston(4944) [Ruby] modules/SpaceCalculation.rb:617 Executing mount command: /usr/bin/mount -o ro /dev/sda1 /tmp/YaST2-04944-k6UK7e/diskspace_mount
2019-04-16 13:53:10 <3> gaston(4944) [bash] ShellCommand.cc(shellcommand):78 mount: /tmp/YaST2-04944-k6UK7e/diskspace_mount: unknown filesystem type 'jfs' (hint: possibly blacklisted, see mount(8)).

See discussion at https://lists.opensuse.org/opensuse-factory/2019-01/msg00549.html.

You can try to remove /etc/modprobe.conf/60-blacklist_fs-jfs.conf or
load the module manually. But in any case the setup is not supported
anymore.

Ancor: YaST could of course inform the user about this.

(In reply to Per Jessen from comment #9)
> I seem to recall you and I having a similar discussion with 15.0?  Yes, see
> bug#1078552.

Ah, you are right :) Yes, and the situation has not changed. The code,
inst-sys, and other stuff is shared with SLE and we (YaST Team) are still
not in charge to decide which FS should be supported and how.

The point is, that some use-cases are just "best effort", but this one is
"actively disabled". In the past, JFS was marked as "best effort", but
product management decided that they want to make it unavailable (of course,
it can be somehow enabled manually, always). Till this is not configurable
(e.g., disabled for SLE, enabled for openSUSE), we can't do much here.

Codestream 15 has a new storage, that's why it may behave differently compared
to Codestream 12 (13) and older.

(In reply to Arvin Schnell from comment #11)
> Thanks for the logs. From the logs:
> 
> 2019-04-16 13:53:10 <1> gaston(4944) [Ruby] modules/SpaceCalculation.rb:617
> Executing mount command: /usr/bin/mount -o ro /dev/sda1
> /tmp/YaST2-04944-k6UK7e/diskspace_mount
> 2019-04-16 13:53:10 <3> gaston(4944) [bash] ShellCommand.cc(shellcommand):78
> mount: /tmp/YaST2-04944-k6UK7e/diskspace_mount: unknown filesystem type
> 'jfs' (hint: possibly blacklisted, see mount(8)).
> 
> See discussion at
> https://lists.opensuse.org/opensuse-factory/2019-01/msg00549.html.
> 
> You can try to remove /etc/modprobe.conf/60-blacklist_fs-jfs.conf or
> load the module manually. But in any case the setup is not supported
> anymore.

Thanks Arvin, I forgot about that discussion.  I'll try that.

(In reply to Per Jessen from comment #13)
> (In reply to Arvin Schnell from comment #11)
> > Thanks for the logs. From the logs:
> > 
> > See discussion at
> > https://lists.opensuse.org/opensuse-factory/2019-01/msg00549.html.
> > 
> > You can try to remove /etc/modprobe.conf/60-blacklist_fs-jfs.conf or
> > load the module manually. But in any case the setup is not supported
> > anymore.
> 
> Thanks Arvin, I forgot about that discussion.  I'll try that.

Just in case anyone reads this - manually loading module 'jfs' worked a treat.  I feel pretty stupid that I forgot about that discussion.