Could you please compile the next versions of the kernel package with vxfs support? That would be much appreciated. Cheers.
Can you provide some justification here? The freevxfs filesystem hasn't been substantially worked on since 2008, and it's read-only support. I'm fairly concerned it will be of very limited value, as vxfs has likely had on-disk format chance in the past 7 years.
Sure. Quite simply I have two SCSI disks coming from an old UNIX machine and I want to mount them to retrieve the data they hold. I don't have access to the UNIX machine anymore.
Your use case is valid, but it isn't really enough for us to enable something distro-wide. What kernel are you currently running?
(In reply to Josh Boyer from comment #3) > Your use case is valid, but it isn't really enough for us to enable > something distro-wide. I get that. My google search showed me however that I'm not the first one struggling with this issue, so this will probably be helpful to a few others in the future. Would there be any potential issue when the support is enabled? What would it take for me to convince you to eventually enable it? > What kernel are you currently running? $ uname -a Linux mymachine.localdomain 4.0.6-300.fc22.x86_64 #1 SMP Tue Jun 23 13:58:53 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux This is the latest available one on an uptodate F22.
https://jwboyer.fedorapeople.org/pub/freevxfs.ko should load and get you whatever support is present in the kernel.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.