Firmware v1.9.2.7 CR4 [Oleg]

hi,

Quote:

---

Originally Posted by Oleg

Have you tried rsize and wsize mounting options?

---

yes

cu,
peter

Quote:

---

Originally Posted by Oleg

Code:

---

rmdir /mnt
reboot

---

Once rebooted it should not mount rootfs and you should follow original instructions.

---

Thanks oleg, it worked perfectly :)

I'm now trying to install packages (gift) from unslung, but there is a libc issue:

Code:

---

[admin@wl /root]$ gift-setup
-sh: gift-setup: not found
[admin@wl /root]$ giftd
giftd: linked against GNU libc!

---

Should I install other libs to run this packages?
Are thy meant to run in chroot?

Quote:

---

Originally Posted by petgun

hi,

yes

cu,
peter

---

So, what? Buffer size is controlled by client, not server, so rsize and wsize controls that. Is not it?

Quote:

---

Originally Posted by elpaso

Thanks oleg, it worked perfectly :)

I'm now trying to install packages (gift) from unslung, but there is a libc issue:

Code:

---

[admin@wl /root]$ gift-setup
-sh: gift-setup: not found
[admin@wl /root]$ giftd
giftd: linked against GNU libc!

---

Should I install other libs to run this packages?
Are thy meant to run in chroot?

---

Well, looks like gift build is broken then. :) Unslung packages are not tested at the moment. Someone should take care of this.

Quote:

---

Originally Posted by mr0mega

I will restart my mac, and see if I have any look with SAMBA :)

---

It appears, that MAC requires support for CIFS, which is not supported by this Samba version.

Quote:

---

Originally Posted by mr0mega

ok, update

on my usb disk there are two folders called Disk and usb, in the nfs section of the settings I added:

/disk
/usb

Now, when I reference these files I get

John-Yourens-Computer:~ johnyouren$ mount -tnfs 192.168.1.1:/disk /Mount
mount_nfs: can't access /disk: Permission denied
John-Yourens-Computer:~ johnyouren$ mount -tnfs 192.168.1.1:/disk /Mount
mount_nfs: can't access /disk: No such file or directory

it seems to flip between permission denied and no such file or directory :S


Also, if I type

smb://192.168.1.1

in my 'Go To Server' box on my mac it won't connect :(

---

You need to setup exports in the right way. Start reading /etc/exports man page. Every line in the exports list should be valid line for the /etc/exports, as it's copied directly. For simple setup you could use this single entry:

Code:

---

/tmp/harddisk 192.168.1.0/24(rw,async,no_root_squash)

---

This will export your storage to all clients on the LAN.
You could then mount it like this:

Code:

---

mount -tnfs -orsize=32768,wsize=32768 192.168.1.1:/tmp/harddisk /mount_point

---

Quote:

---

Originally Posted by Oleg

So, what? Buffer size is controlled by client, not server, so rsize and wsize controls that. Is not it?

---

..my client is a DBox2 and I changed rsize/wsize > 8192 without any success...'mount' always shows 8192...smaller is possible but not > 8192

What do you say to the invisible files > 2GB?

Quote:

---

Originally Posted by petgun

..my client is a DBox2 and I changed rsize/wsize > 8192 without any success...'mount' always shows 8192...smaller is possible but not > 8192

What do you say to the invisible files > 2GB?

---

This seems to be a limitation of the current kernel/daemon:

Code:

---

/*
 * Maximum blocksize supported by daemon currently at 8K
 */
#define NFSSVC_MAXBLKSIZE      8192

---

Quote:

---

Originally Posted by petgun

What do you say to the invisible files > 2GB?

---

Do you've this with samba/ftp only?

hi,

Quote:

---

Originally Posted by Oleg

Do you've this with samba/ftp only?

---

yes

will you change the rsize/wsize limitation of the current kernel/daemon in an upcoming Version of your brilliant Firmware?

cu,
peter

Quote:

---

Originally Posted by petgun

hi,

yes

---

they do not support large files.

Quote:

---

will you change the rsize/wsize limitation of the current kernel/daemon in an upcoming Version of your brilliant Firmware?

---

Probably, but I need to check on this first.

Quote:

---

Originally Posted by Oleg

they do not support large files.

---

..Samba? It was ok with the JOCKYW2001 and original WL-HDD Firmware.

Quote:

---

Probably, but I need to check on this first.

---

thank you! I'm sure there will be a little performance boost in r/w speed

cu,
peter

Quote:

---

Originally Posted by Oleg

This seems to be a limitation of the current kernel/daemon:

Code:

---

/*
 * Maximum blocksize supported by daemon currently at 8K
 */
#define NFSSVC_MAXBLKSIZE      8192

---

---

yes, set it to 32768, it normally won't cause any prob

concerning the samba >2GB prob, what samba version did you build?

Quote:

---

Originally Posted by petgun

What do you say to the invisible files > 2GB?

---

Quote:

---

Originally Posted by Oleg

Do you've this with samba/ftp only?

---

You can try to format the drive as another filesystem. I guess you've formatted it as fat32. Because this is a limitation of fat32, depends on how the system uses integers the limit per file can be 2Gb (if the system uses signed integers) or 4Gb (if the system uses unsigned integers). NTFS or linux file system should solve this problem.

Quote:

---

Originally Posted by kfaessen

You can try to format the drive as another filesystem. I guess you've formatted it as fat32..

---

no, it's ext3 formatted!

cu,
peter