On 10/26/2017 08:01 PM, Akemi Yagi wrote:> On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: > >> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> wrote: >>> On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: >>> >>>> On 04/18/2017 12:54 PM, H wrote: >>>>> A couple of days ago I submitted a request to ElRepo and kmod-jfs >>> is >>>> now available for CentOS 7 as well. >>>> Did not have a need to mount a JFS disk on my CentOS 7 system until >>> today >>>> and it does not want to be mounted, instead complaining "unknown >>> filesystem >>>> type 'jfs'". I do have kmod-jfs installed. >>>> >>>> The commandline I use is: >>>> >>>> mount -t "jfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" >>> /mnt/share >>>> I am doing this as root and /mnt/share has been created for the root >>> user. >>>> What am I doing wrong? Does anyone have JFS volumes mounted under >>> CentOS 7? >>> ?The kmod-jfs package needs to be rebuilt against the EL7.4 kernel. ? >>> >>> ?We will update the bug report ( >>> ?http://elrepo.org/bugs/view.php?id=728 ) >>> when the updated version is ready. >>> >>> Akemi >> Where does one see which kernel version the release is intended for? I >> should add that I installed it from elrepo earlier today on a current >> computer, not some time ago... No error messages. >> > ?Try the following command on a computer you had kmod-jfs installed: > > ?$ ls -l `find /lib/modules -name jfs.ko` > > It will show where the module was installed (in the extra/ directory) and > may show symbolic links to other kernel versions (if any) that are > compatible. > > In the case of the kmod-jfs package, there was a kABI breakage when going > from el7.3 to el7.4. As a result, what was built against el7.3 was broken > in el7.4. It has now been built against the el7.4 kernel. This one is not > backward compatible with earlier (< 7.4) kernels. > > Akemi > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centosI tried the above and this is the output: lrwxrwxrwx. 1 root root???? 51 Oct 26 17:56 /lib/modules/3.10.0-514.21.2.el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7.x86_64/extra/jfs/jfs.ko lrwxrwxrwx. 1 root root???? 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.1.el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7.x86_64/extra/jfs/jfs.ko lrwxrwxrwx. 1 root root???? 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.2.el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7.x86_64/extra/jfs/jfs.ko -rw-r--r--. 1 root root 302480 Apr 16? 2017 /lib/modules/3.10.0-514.el7.x86_64/extra/jfs/jfs.ko I also ran yum update again but it did not pick up kmod-jfs although it was just updated. How long time does it typically take for an updated package to become available?
On Thu, Oct 26, 2017 at 5:22 PM, H <agents at meddatainc.com> wrote:> On 10/26/2017 08:01 PM, Akemi Yagi wrote: > > On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: > > > >> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> > wrote: > >>> On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: > >>> > >>> ?We will update the bug report ( > >>> ?http://elrepo.org/bugs/view.php?id=728 ) > >>> when the updated version is ready. > >>> > >>> Akemi > >> Where does one see which kernel version the release is intended for? I > >> should add that I installed it from elrepo earlier today on a current > >> computer, not some time ago... No error messages. > >> > > ?Try the following command on a computer you had kmod-jfs installed: > > > > ?$ ls -l `find /lib/modules -name jfs.ko` > > > > It will show where the module was installed (in the extra/ directory) and > > may show symbolic links to other kernel versions (if any) that are > > compatible. > > > > In the case of the kmod-jfs package, there was a kABI breakage when going > > from el7.3 to el7.4. As a result, what was built against el7.3 was broken > > in el7.4. It has now been built against the el7.4 kernel. This one is not > > backward compatible with earlier (< 7.4) kernels. > > > > Akemi > > I tried the above and this is the output: > > lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.21.2. > el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.1. > el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.2. > el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > -rw-r--r--. 1 root root 302480 Apr 16 2017 /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko >?The output shows that the version of the installed kmod-jfs is for kernel-?3.10.0-514.el7.x86_64 and is compatible with all -514 kernels (el7.3). I also ran yum update again but it did not pick up kmod-jfs although it was> just updated. How long time does it typically take for an updated package > to become available? >?It is syncing to mirrors. It may show up any time between now and several hours later. Akemi
On 10/26/2017 08:37 PM, Akemi Yagi wrote:> On Thu, Oct 26, 2017 at 5:22 PM, H <agents at meddatainc.com> wrote: > >> On 10/26/2017 08:01 PM, Akemi Yagi wrote: >>> On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: >>> >>>> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> >> wrote: >>>>> On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: >>>>> >>>>> ?We will update the bug report ( >>>>> ?http://elrepo.org/bugs/view.php?id=728 ) >>>>> when the updated version is ready. >>>>> >>>>> Akemi >>>> Where does one see which kernel version the release is intended for? I >>>> should add that I installed it from elrepo earlier today on a current >>>> computer, not some time ago... No error messages. >>>> >>> ?Try the following command on a computer you had kmod-jfs installed: >>> >>> ?$ ls -l `find /lib/modules -name jfs.ko` >>> >>> It will show where the module was installed (in the extra/ directory) and >>> may show symbolic links to other kernel versions (if any) that are >>> compatible. >>> >>> In the case of the kmod-jfs package, there was a kABI breakage when going >>> from el7.3 to el7.4. As a result, what was built against el7.3 was broken >>> in el7.4. It has now been built against the el7.4 kernel. This one is not >>> backward compatible with earlier (< 7.4) kernels. >>> >>> Akemi >> I tried the above and this is the output: >> >> lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.21.2. >> el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. >> x86_64/extra/jfs/jfs.ko >> lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.1. >> el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. >> x86_64/extra/jfs/jfs.ko >> lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.2. >> el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. >> x86_64/extra/jfs/jfs.ko >> -rw-r--r--. 1 root root 302480 Apr 16 2017 /lib/modules/3.10.0-514.el7. >> x86_64/extra/jfs/jfs.ko >> > ?The output shows that the version of the installed kmod-jfs is for > kernel-?3.10.0-514.el7.x86_64 and is compatible with all -514 kernels > (el7.3). > > I also ran yum update again but it did not pick up kmod-jfs although it was >> just updated. How long time does it typically take for an updated package >> to become available? >> > ?It is syncing to mirrors. It may show up any time between now and several > hours later. > > Akemi > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centosThank you, works great!