SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It seems that NTFS write support has reached a point where it is stable and safe under *nix (finally!). I don't like using FAT32 for shared data storage partitions on dual-boot machines due to the 4GB file size limit. It keeps me from twiddling with DVD iso's and large video files. I'm about to do a major rebuild of my server(s) and desktop. I want to use a dedicated hard drive with an NTFS partition in the desktop for the shared data after the conversion and plan to use the NTFS-3G driver, along with the requisite Fuse.
Why isn't there a more recent Fuse binary in any Suse repo that I check? The newest I have found is 2.6.1, and when an NTFS partition gets mounted, the NTFS-3G driver pukes this at me:
Code:
WARNING: Deficient FUSE kernel module detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it's made sure the ntfs-3g process
naturally terminates after calling 'umount'. The safe FUSE kernel
driver is included in the official Linux kernels since version
2.6.20-rc1, or in the FUSE 2.6.0 or later software packages,
except the faulty FUSE version 2.6.2. Please see the next page
for more help: http://www.ntfs-3g.org/support.html#fuse26
So what's up? The current version of Fuse is 2.6.3, which Suse's default kernel apparently doesn't have compiled in (or any version). Is there a binary of 2.6.3 anywhere out there? Is the warning I am getting just alarmist? Will I be fine until someone compiles a newer version (I don't care for installing from source, BTW)?
You could look below for the 2.63 binary or compile your own, also there is a 2.20 kernel rpm somewhere (I'd use webpin to search for it), I installed it and had a few issues so went back to 2.18.
Ensure you at the ./configure step include the option to make as a kernel module. I'm not sure of the exact option but when you run it you'll get the correct message.
Here's the latest:
By adding the repo suggested by google01103 to my usual list of suspects, I now have ntfs-3g v. 1.328-2.1 and FUSE v. 2.6.3-4.1, both of which are supposed to fully meet the requirements listed on the ntfs-3g web site. Now mounting an NTFS partition with ntfs-3g nets me:
Code:
WARNING: Deficient Linux kernel detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it's made sure the ntfs-3g process
naturally terminates after calling 'umount'. If you wish this
message to disappear then you should upgrade to at least kernel
version 2.6.20, or request help from your distribution to fix
the kernel problem. The below web page has more information:
http://www.ntfs-3g.org/support.html#fuse26
The listed web page tells nothing useful.
Suse 10.2 is currently using 2.6.18.8 and a recompile hardly seems worth the effort if such handy binaries are available. Heck, even Knoppix uses 2.6.19. Who would be using such a recent kernel yet? Isn't this driver stable with a less bleeding-edge kernel?
Am I missing something, or should I just cope with it and wait for Suse to start using a newer kernel?
J
PS - Perhaps someone knows of another ntfs driver with stable write-support that I could try???
You should only get that message if you didn't force the 2.6.3 version into the kernel.
Forget about the rpm version --it's quite easy to unpack and compile the source. You don't even need to unpack the tar / gzip version as this can be done from KDE with the built in ARK archiver extractor.
blackdog:/ # mount -t ntfs-3g /dev/hde6 /windows/F
blackdog: / #
blackdog:/ # mount -l
/dev/hdg7 on / type reiserfs (rw,acl,user_xattr) []
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hdg8 on /home type reiserfs (rw,acl,user_xattr) []
/dev/hde1 on /windows/C type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksiz e=4096) []
/dev/sdb1 on /windows/D type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksiz e=4096) []
/dev/hde5 on /windows/E type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksiz e=4096) []
/dev/hde7 on /windows/G type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksiz e=4096) []
/dev/sda5 on /windows/H type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksiz e=4096) []
securityfs on /sys/kernel/security type securityfs (rw)
/dev/hde6 on /windows/F type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksiz e=4096) []
blackdog:/ #
If all else fails try and uninstall FUSE, reboot and re-install again preferably compiling.
In general I'm not a big fan of RPM method anymore. That was fine way back but there are much better software installation methods now like SMART.
The product NTFS for Linux is listed as being $29.95 for a digital download. It comes as a tar file. Just extract to the /tmp folder or anypace in your /home/user folder. Do a su command and enter your root password and then you run the terminal command from the /tmp folder:
sh ./install.sh
When run from the /tmp folder it will add itself to the /fstab file, but duplicates the original ntfs entry. I delete the added line and make my orginal ntfs look like this:
Use your partition name in place of my sda1 and your folder name in place of the /Windows. In general you can use the SuSE default entry for your read only ntfs setup, but you change the driver from ntfs to ufsd and you remove the ro option command.
Afraid I had bad luck and experience with ALL paragon products -- the Partition / backup / restore stuff was a JOKE (plus a time waster).
FUSE is 100% FREE (open source) and it WORKS properly.
I regularly backup large Windows VM's to NTFS folders (USB extenal disks attached to a Linux server) consisting of 15 - 20GB each . Never a single problem.
FUSE 2.6.3 with ntfs-3g-1.0
For a decent backup / restore program look at this website. Thes products WORK every time.
...
Forget about the rpm version --it's quite easy to unpack and compile the source. You don't even need to unpack the tar / gzip version as this can be done from KDE with the built in ARK archiver extractor.
-snip-
In general I'm not a big fan of RPM method anymore. That was fine way back but there are much better software installation methods now like SMART...
???
I'll try installing from source, but your quote is kind of weird...
SMART is exactly what I use because yast's software management is a joke.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.