yashsingh1/xdaforums huggingface dataset:
[Networking] jfluckey:
Thanks for the reply. I will try to go the route of the CIFSManager after I verify that I can get it to mount via the busybox mount command.

On my server, I have the following in my /etc/exports file:

/media/sdc1 192.168.1.0/24(rw,sync,no_subtree_check)

Again, I am running the nightly CM9 for the touchpad (latest release 3/30) so I am assuming the kernel change by brian_o'fish is included.

I then ran:

su
busybox mount -t nfs 192.168.1.149:/media/sdc1 /sdcard/mounts/shows/

but I get the response: No such device

I was able to mount on my server for a test just fine. So, what did I miss along the way?

I forgot to mention, the permissions for my mount point are d---rwxr-x. I apologize for my ignorance. Like others, I would like to access media on my tablet.
[Networking] brian_o'fish:
Things to check:

Have a look at /proc/filesystems - do you see nfs in there? If not, maybe you need to load a kernel module on your device for nfs client support. My contribution was just to the busybox mount code; I have no idea about the state of the kernel for devices I don't own.

After

-t nfs

add

-o nolock

. When I leave that out I get a "connection refused", but maybe that's different in your situation.

First run

su

alone to get a root shell, then the busybox command. Any change? There might be a difference in PATH and you run the wrong busybox. The one that works should be in /system/xbin/busybox, afaik.

If that still does not help, get a root shell, run

type busybox

to see the full path of the busybox that would get called, then run

strings /path/of/that/busybox | grep nfs

- that should show you some lines from the executable that won't be there if you have a busybox without nfs mount support. Mine shows:

unknown nfs status return value: %d
unknown nfs mount parameter: %s=%d
unknown nfs mount option: %s%s
nfs socket
nfs bindresvport
nfsprog
nfsvers
[Networking] jfluckey:
All the busybox stuff was there as you assumed with the same executables as you have. However, I did not have nfs in /proc/filesystems. I saw ntfs if that is similar or helpful. Do I need to drop some files on my system or does this require messing with the kernel? AS always, your help is greatly appreciated.
[Networking] MountainX:
ntfs is a microsoft file system (I think it stands for new technology file system and it came out with Windows NT). obviously, that's unrelated

nfs is a Sun/unix/linux protocol - it stands for network file system. See https://en.wikipedia.org/wiki/Network_File_System
[Networking] brian_o'fish:
NTFS has nothing to do with it.

I just had a look at the tenderloin (touchpad) kernel support in CM9. There is no NFS built into the kernel, or you would see it in /proc/filesystems, and there is no loadable NFS client module either.

So, right now, you would have to set up a kernel build environment, locate the right kernel tree for your device, and set about compiling the module yourself. As I don't own the device, I cannot help you any further, sorry.

However, I dropped an E-Mail to the person who last updated the tenderloin kernel, asking whether he could include the NFS client. We'll see how this goes.
[Networking] jfluckey:
Thanks. I should have edited my post as I did a google search for it after I asked the question. I knew nfs, but it was the first time seeing ntfs. :o

---------- Post added at 08:22 AM ---------- Previous post was at 08:15 AM ----------

I really appreciate this. You went out of your way to send the e-mail. I would have posted in the rootzwiki forums last night, but I couldn't get an account set up on my touchpad (browser was having problems with key captcha puzzle), and I was too lazy to go downstairs. :)
[Networking] jfluckey:
How did you find the last compiler of the kernel?
[Networking] jcsullins:
I've created an 'update' package to add the required nfs modules to the latest

touchpad nightlies.

http://dl.dropbox.com/u/53916521/cmtouchpad/update-touchpad_nfs_modules-for-cm9_20120404-signed.zip

Use CWM to install. Also, after boot, will need to run: "su" then "modprobe nfs"

before mounting.
[Networking] jfluckey:
This is the best news all week. I have been feeling like a stalker trying to find someone with the ability to do this. Thank you verrrrry much.
[Networking] guano30:
Hi!

Found that amazing Post and tried your files.

Installing and modprobe is OK.

But get several error messages from Terminal when I try to mount my NFS Share.

How must a NFS Mount look like for the HP Touchpad?

mount -t nfs IP-Adresse:/var/mnt/hdd /sdcard/mnt/nfs -o rw,intr,soft,udp,nolock,rsize=8192,wsize=8192

wont work.

Thanks for your amazing work also with the MIC on the Touchpad!
[Networking] jfluckey:
You need to use the busybox command found earlier in this thread. Are you sure you are hosting nfs from your server? I will respond later when I have my TP handy for the actual commands I use.

1.) The modprobe needs to be done after reboot.

2.) The busybox mount needs to be done after modprobe.
[Networking] guano30:
woo woo woo........

Yep with busybox it works!

I have a server 2008 running nfs server from hanewin.....

cifs sucks....... I also had massive Problems using it with my Dreambox....

So i decided to use Hanewin and hey........ it runs like Hell with NFS.....

Many Thanks!!

EDIT:

Wich Parameters you use ?

Are there improvements wich speed up the connection? thinking about rsize and wsize.......notree..........

A chance to load it automaticly when TP starts??

EDIT 2:

damn!

After restarting the TP modprobe nfs dont work anymore :(

there is an error message

i flashed the zip again but nothing happens.......

what do i wrong?
[Networking] jfluckey:
Glad it worked out for you (initially).

You don't need to reflash each time. You just have to run "su" "modprobe nfs". You sure you used "su" to gain super user?

I haven't automated it after reboot. I did write a script, but I haven't found out how to run it at boot. Therefore, I just open the script and copy/paste the commands each time I reboot.

As far as parameters, I don't think I used anything other than what was posted in this thread. I will verify when I get home. However, with parameters I am using, I haven't had any problems playing 720p mkv's.
[Networking] guano30:
its crazy!

All worked fine......

After Rebooting and going to terminal i got that error message.....

I installed an other Terminal app that gets SU rights...... so thats not the point...

Dont know what went wrong........

I do nothing else than reboot the device.......

any ideas ?

EDIT:

Well I guess somehow and I dont know how I damaged the Filesystem with that Experiment.

On my 2nd Touchpad everything is allright, also after reboot.

maybe it belongs in which order I install both?

first busybox then the nfs.zip ?

like this I do it on my 2nd Touchpad......

well I ll do a backup from 2nd and flash it on the demaged........ lets see if this work!
[Networking] e5g:
Have the same problems on a Mele A2000 device:

Have added "lockd.ko", "nfs.ko" and "sunrpc.ko" manually with:

busybox mount -o remount,rw /dev/block/nandd /system
busybox cp -rf "/mnt/sdcard/Download/nfs_modules/system/lib/modules/lockd.ko" "/system/vendor/modules/"
busybox cp -rf "/mnt/sdcard/Download/nfs_modules/system/lib/modules/nfs.ko" "/system/vendor/modules/"
busybox cp -rf "/mnt/sdcard/Download/nfs_modules/system/lib/modules/sunrpc.ko" "/system/vendor/modules/"
busybox mount -o remount,ro /dev/block/nandd /system

Don't know if /system/vendor/modules/ is the right place, but busybox find / -name *.ko has only hits in this directory...

Tested after a reboot (my new *.ko files exists):

# busybox modprobe nfs
modprobe: chdir(/lib/modules): No such file or directory

# busybox insmod nfs
insmod: can't insert 'nfs': No such file or directory

# busybox lsmod
Module Size Used by Not tainted
sun4i_sndspdif 2633 0
sndspdif 2871 1
sun4i_spdma 4369 1
sun4i_spdif 6383 1
gpio_sw 96389 0
rtl8150 8910 0
mcs7830 6557 0
qf9700 8513 0
asix 22500 0
mali 130113 8
ump 42126 15 mali
sun4i_ir 4340 0
nand 118930 10

# cat /proc/filesystems
nodev	sysfs
nodev	rootfs
nodev	bdev
nodev	proc
nodev	tmpfs
nodev	devtmpfs
nodev	binfmt_misc
nodev	debugfs
nodev	sockfs
nodev	pipefs
nodev	anon_inodefs
nodev	rpc_pipefs
nodev	configfs
nodev	devpts
ext3
ext2
ext4
nodev	ramfs
vfat
msdos
iso9660
nodev	nfs
nodev	cifs
ntfs
nodev	autofs
nodev	fuse
fuseblk
nodev	fusectl
udf

A mount test:

# busybox mount -o vers=1 -t nfs 192.168.x.y:/foo /mnt/sdcard/foo
mount: mounting 192.168.x.y:/foo on /mnt/sdcard/foo failed: Connection refused

# busybox mount -o vers=2 -t nfs 192.168.x.y:/foo /mnt/sdcard/foo
mount: mounting 192.168.x.y:/foo on /mnt/sdcard/foo failed: Connection refused

# busybox mount -o vers=3 -t nfs 192.168.x.y:/foo /mnt/sdcard/foo
mount: mounting 192.168.x.y:/foo on /mnt/sdcard/foo failed: Protocol not supported

# busybox mount -o vers=4 -t nfs 192.168.x.y:/foo /mnt/sdcard/foo
mount: NFSv4 not supported
mount: mounting 192.168.x.y:/foo on /mnt/sdcard/foo failed

System info:

# busybox uname -a
Linux localhost 3.0.8+ #47 PREEMPT Fri Sep 7 12:35:00 CST 2012 armv7l GNU/Linux

Any idea?

EDIT: Seems that the modules are not compatible to the mele kernel:

root@android:/system/vendor/modules # insmod nfs.ko
insmod: init_module 'nfs.ko' failed (Exec format error)
[Networking] Thailandian:
Again I hope I'm not too late to help others, but I ended up solving this problem for CM7.2 on my Galaxy Mini, simply by installing the version of BusyBox that comes with SuperCharger_Starter_Kit.

Download and instructions can be found here: http://xdaforums.com/showpost.php?p=18703418&postcount=5021

SuperCharger_Starter_Kit can install several files besides besides BusyBox, but at least in my case, the script said the others were already up-to-date or not appropriate for my rom.

Once the uncastrated BusyBox was installed, I was able to mount shares again using the syntax I described earlier in this thread.

So it seems, at least for Cyanogenmod 7.2 Official for Galaxy Mini, that the problem is only with SnoozyBox ;). Support for NFS must still exist in the kernel.

Hope this helps someone. :fingers-crossed:
[Networking] rregn:
mount: mounting xxx on xxx failed: No such device on Huawei U 8825-1
[Networking] KenSharp:
/etc/fstab cannot be found

I seem to be the only one with this message:

# mount -t nfs -o guest,rw -v hdd1.lan:/shared\ files
mount: can't read '/etc/fstab': No such file or directory
[Networking] MrObvious:
Do you have that file? If you do you might try chmod 777 on it just to test.
[Networking] roycevv:
Thanks for your sharing! I have the same question with this!;)
[Networking] Edge-Case:
The kernel object files may exist on the ram disk, if thats the case, those file you see there get loaded up into ram at boot, hence ram-disk. After rebooting the phone the files get loaded from the image again into ram, your changes only exist in ram and are therefore volitile. Anyways I shouldn't act like I know anything.

Where did you get the *.ko files, they might be able to be built with the kernel, or it might be as simple as unpacking the ramdisk puting them in there and repacking it, though I haven't figured out how to use the ramdisk tools mkbootimg or umkbootimg and stuff, but I can modify Android.mk files and variables here and there to get the job done from source with brunch so at least there's a way.

Hope that helps. How would I get the source for those modules? Where they 'optimized' for embeded devices, specifically Android maybe?

Edit:Maybe try checking the permissions of the ko files, I know Android can be real 'paranoid' about things the users do to it, basically a lot of setting on permissions get baked into the ramdisk so source is the place to mod those variables for persistance, maybe try "chmod 755 <file>" or "busybox chmod 755 <file>" before trying to load the modules, it wont last after a reboot, but if you dont turn it off every night it wont be too bad. If you keep getting permission denied error I am sure the beans need to be cooked with the jelly.

Edit2: If 755 doesn't work other args sometimes go like o+x (owner, add executable, a+rwx ( all, add read/writable and executable), 777, 0755, 0777; and more rarely 00755 or even stranger perms that I don't understand like 06755 .

Edit3: "Well if your 555 I'm 666..."
[Networking] tobias.pal:
nfs mount Protocol error

Thanks guys, you pointed me to the right direction to use busybox mount instead of android mount. Unfortunately I got Protocol not supported:

busybox mount -t nfs 192.168.2.1:/usr/portage /data/gentoo/usr/portage -o nolock
mount: mounting 192.168.2.1:/usr/portage on /data/gentoo/usr/portage failed: Protocol not supported

But I got around it by explicitly mounting nfsv2. Seems that my kernel only has v2 support but not v3. I don't mind as I don't need v3, won't be using files >2GB. This is what works for me:

busybox mount -t nfs 192.168.2.1:/usr/portage /data/gentoo/usr/portage -o nolock,vers=2
[Networking] tadeus666:
This usage of mount works good at my device

busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs x.x.x.x:/mnt/p2 /storage/emulated/legacy/nfs

BUT

I only can look at this mountpoint with the commandline. If I am using a file manager like "antek explorer", the nfs folder is empty

Why????
[Networking] jcespi2005:
Many thanks mate ;) i have now this working on my Minux X7 :D and can access an NFS Synology resource...
[Networking] brotbuexe:
Same issue for me, did you found a solution?
[Networking] mad_ady:
I haven't tested it, but your files may be shared back with their original permissions/users and groups (from the server) which will most likely not match the ones on the client. Try out some mount options like all_squash or try to add r-x rights for folders in the "other" section (e.g. rwxr-x-r-x).

Here's a site with some guidelines in NFS troubleshooting:

http://www.troubleshooters.com/linux/nfs.htm#_If_it_mounts_but_cant_access
[Networking] ricardo85x:
I have the same problem.

Any solution?

On my export I have this:

/overlay/storage 192.168.1.150(rw,sync,no_subtree_check,all_squash)

And I am mounting like this:

/system/xbin/mount -o nolock,rw,hard,intr -t nfs 192.168.1.1:/overlay/Ricardo /storage/emulated/legacy/WD

I only can see the files with root on terminal.

Thanks
[Networking] mad_ady:
If you are running android 4.2 or later you are affected by the mount namespace "security feature". Look it up, but in short it means that if a program mounts something under /storage only that user will see the mounpoint.

If your kernel/rom supports it, try mounting in /mnt.
[Networking] brotbuexe:
Supersu v1.93 has a new feature.

With 'su --mount-master -c busybox mount...' I can access the files within apps.
[Networking] mad_ady:
Sweet! I'll certanly give it a try! Thanks for sharing. I will post back results.
[Networking] ricardo85x:
Almost there :good:

Hi with superSU I was able to mount and see the files with rootBrowser. But apps that does not have root support can't see the files.

Do you know if there are a way to open a android app with root permission?

Or should I ask the developer to add root support to the app?

Thanks!
[Networking] mad_ady:
I too was able to mount my nfs shares with the command above! I was also able to access the content from non-root apps. I will post a detailed explanation later today!
[Networking] brotbuexe:
For me it works when I had the app, I want to access the mounted folder with started before mounting.

I think the "su --mount-master" works by mounting the folder in all running namespaces.
[Networking] mad_ady:
Here's my recepie for mounting NFS shares on my Galaxy S3, running NeatRom 2.8 (Derived from SlimKat 2.8) and with Boeffla-Kernel:

#remount the root filesystem rw so that we can create the mountpoint
/sbin/busybox mount -o remount,rw /
#create the mountpoint
/sbin/busybox mkdir -p /mnt/nfs/Download
#make the mountpoint world readable so that all user apps can access it
/sbin/busybox chmod 777 /mnt/nfs
/sbin/busybox chmod 777 /mnt/nfs/Download
#remount / as ro
/sbin/busybox remount,ro /
#mount the actual NFS share (on 192.168.1.5:/DataVolume/Download
su --mount-master -c "/sbin/busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.5:/DataVolume/Download /mnt/nfs/Download"
#check that it was mounted
mount | grep /mnt/nfs/Download

Using this method (and having world readable permissions on my shared files) I am able to access the files both with a root explorer (ES File Manager) and with non-root apps (MXPlayer, QuickPic). Without running the chmod on the created folders I am only able to access them with a root explorer.

Let me know if you need additional help, and a million thanks to [MENTION=1710210]brotbuexe[/MENTION] for pointing out the mount-master trick (I was actually looking into injecting commands into adb before finding out of this switch).
[Networking] mad_ady:
I made a simple Tasker scene similar to Cifs Manager to mount my NFS shares. If there are fellow Tasker users among you, I'd like to get some feedback: http://xdaforums.com/showthread.php?p=50480146

The task basically uses the commands above to do the dirty work.
[Networking] ricardo85x:
Great!

It did the job!

thanks you!
[Networking] mad_ady:
I did a basic speed test download in the same conditions to test the speed difference between samba and nfs over my 802.11g Wifi and although I expected NFS to be faster, I never expected it to be almost twice as fast as Samba!

root@android:/ # ls -l /mnt/cifs/Kits/250M
-rw--w---- 503 system 262144000 2014-02-20 20:55 250M
root@android:/ # time dd if=/mnt/cifs/Kits/250M of=/dev/null
512000+0 records in
512000+0 records out
262144000 bytes transferred in 200.061 secs (1310320 bytes/sec)
3m20.62s real 0m0.97s user 0m11.37s system
root@android:/ #
root@android:/ # time dd if=/mnt/nfs/Kits/250M of=/dev/null
512000+0 records in
512000+0 records out
262144000 bytes transferred in 119.271 secs (2197885 bytes/sec)
1m59.30s real 0m1.29s user 0m8.70s system
root@android:/ #
root@android:/ # mount | grep Kits
192.168.1.5:/DataVolume/Kits /mnt/nfs/Kits nfs ro,relatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.5,mountvers=3,mountproto=tcp,local_lock=all,addr=192.168.1.5 0 0
//192.168.1.5/Kits /mnt/cifs/Kits cifs rw,relatime,sec=ntlm,unc=\\192.168.1.5\Kits,username=adrianp,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.5,unix,posixpaths,serverino,acl,rsize=16384,wsize=131007,actimeo=1 0 0
[Networking] Smidley:
Very happy to find NFS baked into this kernel (looking at you, Apple!), but running the mount command prefixed with "busybox" would not work for me on the FTV Stick. No output to stdout/stderr, and it's return code was 0, but nothing actually mounted -- not sure what was going on there. Of course, just running "mount -o ..." isn't an option, because that's the wonky /system/bin/mount that doesn't work à la Invalid Argument.

Instead, I had to give the full FS path of the busybox mount binary in /system/xbin to finally get it working.

[B]/system/xbin/[/B]mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.xxx.xxx.x.x:/your/nfs/share /mnt/sdcard/YourLocalFolder

Thanks for pointing me in the right direction.
[Networking] jp_rock:
This works for me, but only after setting setenforce permissive.

Has anybody had success in mounting nfs without disabling SELinux protections?
[Networking] fakir81:
Hi, Android 4.0.4, kernel 3.0.8+, nodev nfs in kernel, busybox update.

I have tried everything, but mounted only this: busybox mount -t nfs -o nolock,ro,hard,intr,vers=2 192.168.1.2:/Share /mnt/sdcard/share

If I write vers=3, Protocol not supported

There are restrictions on the size of files in the second version.

Is it possible that the kernel supports only the 2nd nfs version?

Sorry my English.
[Networking] mad_ady:
Yes. NFS v3 requires a different kernel module that you probably don't have.
[Networking] jazzl:
Howdy experts,

I´ve just rooted my Huawei P8 with Marshmellow, and I´m trying to mount Nfs shares on my phone.

It fails:

1|shell@HWGRA:/mnt $ busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.178.10:/Film5 /mnt/Film5

rd,intr,vers=3 -t nfs 192.168.178.10:/Film5 /mnt/Film5 <

mount: nfs bindresvport: Permission denied

mount: mounting 192.168.178.10:/Film5 on /mnt/Film5 failed: Bad file descriptor

This is when using adb shell from my computer. "Busybox Free" is given root perm in SuperSu. I also get a permission denied error when using mkdir Film5 in /mnt - from the adb shell as well. Hence, I found something called Root Toolbox which also needed root permissions, and there I managed to mkdir Film in /mnt.

But when giving the same command there as first stated to mount the nfs access, I´m receiving an I/O error.

Is somebody experienced with how to do this the simplest way?

Btw, the nfs share is set up on my PC with a program called Hanewin, and I access it with no problem from OSMC from my Raspberry.

Any hints on how to do this with smb shares instead are welcome too.

Oh, and the interesting thing is that in hanewin, the attempt to mount via android shows up in "mounts" next to what´s mounted on the raspberry.

Thanks!
[Networking] ricardo85x:
You could try with vers=2

I have to do that to work with my raspberry.
[Nexus One Q&A, Help & Troubleshooting] carlost24:
I'm currently on modaco r21 sense I want to improve my battery life how can I go about doing that? Can I flash a kernel if so which one?
[Nexus One Q&A, Help & Troubleshooting] zizoty:
Flash intersectrave or pershoot kernels. Try all the kernels and see which one fit you best, no harm to your phone if you keep on flashing kernel. Dont ask question in this forum because its for DEV only. Use the general forum for all your question.
[Nexus One Q&A, Help & Troubleshooting] imfloflo:
Hi.

You can improve your battery life by :

-reading forum rules

-usin search button

-poosting in good section

-be polite

F.
[Nexus One Q&A, Help & Troubleshooting] techlogik:
IntersectR doesn't support Desire Rom for the newer 34 Kernel.

The last Kernel is 33.5 back in late May that was updatedt that is undervolted and will wor fine on Desire R21. Run the 925 CFS version and you are good to go.

4th Kernel down.

http://www.mediafire.com/intersectRaven
[Nexus One Q&A, Help & Troubleshooting] carlost24:
Thanks alot tech I really appreciate it, was actually having some trouble trying to figure out which one was right for me I want to improve my battery but not give up to much speed, thanks again tech...

I was also wondering how I can make my phone run a bit faster I have setcpu an its at 768MHz I was wondering how I could improve that without frying my phone, don't even know if its possible to fry your phone but yea...
[Hero, G2 Touch General] avenge the rage:
Hey guys, i have got a ROM on my phone tha is saying low space, so i now want to put my apps onto my SD card. I have a 16GB SD in there, so is there any tutorials or anything on how to do it?

Thanks
[Hero, G2 Touch General] bonesy:
http://xdaforums.com/showthread.php?t=535232&page=18]

Try there but depending what rom you use...You shoukd be able to flash amon_ra recovery and partition sdcard (PLEASE BACK UP CARD FIRST) with an ext file system and the rom will do the rest!