RE: [nslu2-linux] Value too large
- It because original distribution of UNSUNG consist SAMBA ver 2. This version has limitation to serve files 2 GB maximum. You have to install SAMBA ver 3. Justipkg updateipkg install sambaAnd keep in mind, that if You want to copy files using copy/paste facility from Windows, the limitation of this application in WIN is 4 GB file size. So if You have bigger files, you must use FTP (any kind).
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Calum Sharp
Sent: Saturday, September 01, 2007 4:59 PM
Subject: [nslu2-linux] Value too large
Hi all, I have a problem with my Unslung Slug.
I have a Linksys/KISS DP558 networked PVR, and I want to backup files
from it to the Slug. This in itself is not the problem - I transfer
the files over via ncFTP.
The problem is that I want to access these files from a Windows PC on
the network, and they are often over 2Gig in size. I cannot access
them, even from the public folder, as they belong to root and are not
I have tried chown/chmod- ing them, but I get the " Value too large for
defined data type" error, same as when I ls them.
Does anyone have any tips I can use to make these files accessible?
I am more than 10 years out of practice with Linux, and can't remember
much of the little I knew then.
I have tried logging as guest (screen login, then guest and blank
password) to run ncftp, but the transferred files still belong to root.
I saw a thread on installing core-utils, but IPKG tells me it
conflicts with BusyBox-links and stops the install.
I think my ideal solution would be to have the files transferred as
belonging to guest.
Thanks in advance.
- HI, thanks for the tip.
However, in my newbi-ishness, I only seem to have made things worse.
I installed Samba V3, and all appeared to go fine.
I checked out http://www.nslu2-linux.org/wiki/Optware/Samba for extra
tips, and followed the instructions there about changing the smb.conf
I am now in the following situation - files over 2Gb still report
Value too Large when I ls the directory via telnet, or try to chown
any files over 2Gb, and, I can no longer map the shared drive on my WinPC.
After some degree of mucking about with varying levels of failure,
when trying to map the drive I can see the Slug as part of the
workgroup, and DISK 2 as the shared drive, but when I try to map it I
get told the Network Path could not be found. If I browse to the
workgroup in Windows, go to Slug, and try to open DISK 2 I get told it
is not accessible (I may not have permissions).
I am unclear on how to set or achieve permissions. I have the
following sections in my sbm.conf (in my network the workgroup is 2
Oliver Close, and the IP range is 196.168.2.xxx - I have commented out
the WINS server line, as I have no idea whether I have a WINS server,
but I presumed if I did it would be my router - that didn't help at
all, so I commented it out)
workgroup = 2 Oliver Close
server string = Slug
netbios name = Slug
# your wins server ip address
#wins server = 192.168.2.1
# the networks you want to allow connections from
hosts allow = 127.0.0.1 192.168.2. 10.0.0.
hosts deny = 0.0.0.0/0
browseable = yes
I am guessing those are the relevant sections to what's going on.
--- In firstname.lastname@example.org, "Piotr Mackowiak" <mackowiakp@...>
> It because original distribution of UNSUNG consist SAMBA ver 2. This
> has limitation to serve files 2 GB maximum. You have to installSAMBA ver 3.
> ipkg update
> ipkg install samba
> And keep in mind, that if You want to copy files using copy/paste
> from Windows, the limitation of this application in WIN is 4 GB filesize.
> So if You have bigger files, you must use FTP (any kind).