Very Computer

        I am new to the whole filesystem setup, and I have only a small
understanding of the "inode" concept, but perhaps the problem is with
inodes.  I have run fsck on the fs, and it reports no errors.  

        What can I do?  How can I prevent this in the future?  

        I have looked for info on this subject, but I could find none in
the HOWTOs, man pages, etc.

                                                Thanks,
                                                Jeremy

Quote:>    I am having some sort of huge problem with my native linux ext2
>filesystem:  If I try to ftp/cp/etc a file larger than 50k to the
>filesystem it reports the error:  File too large.  However, I have over
>60 mbytes free for the drive!  Even if I delete files to "make more room"
>it doesn't make any difference.  I can however dump 100 20K files to the
>filesystem.

Try looking in the man pages for mkfs (more specifically the one for e2fs)
and see if there is some wierd parameter for limitiing the file size or
for causing the OS to allocate disk space in some huge extents. (I would
check this for you, but I don't have a linux machine handy here at work.)
If you find that there is a way to limit this, then perhaps that was done
to your file system when it was created.  The only way to fix this would be to
back up the ailing filesystem (either onto another or to tape/floppy with
tar) and then re-format the filesystem with mkfs...

Hope it helps,

- Bob
--
===============================================================================

Littleton, CO, USA                        WWW:    http://www.rmii.com/~kneusel
===============================================================================

Quote:>>>>> "Jeremy" == Jeremy J Smith <jjsst2> writes:

    Jeremy> I can however dump 100 20K files to the filesystem.

This sounds like you have somehow set a user limit on maximum file
size. Try using the command ``limit'' (if you use tcsh as your shell)
or the command ``ulimit -a'' (if you are using bash as your shell).

These commands should show you the current limits _for that session_!

I can reproduce your problem, if I do the following: (in tcsh)

   Yes?> limit filesize 10
   Yes?> limit
   cputime         unlimited
   filesize        10 kbytes
   datasize        unlimited
   stacksize       8192 kbytes
   coredumpsize    0 kbytes
   memoryuse       unlimited
   Yes?> cat /dev/zero >tesfile
   cat: write error: File too large
   Yes?> unlimit filesize
   Yes?> cat /dev/zero >testfile

... testfile just grows and grows...

Now the questions arises - where were this limit setup? Try

    grep limit /etc/profile /etc/*rc ~/.*login ~/.*rc

and see if you find it.

Good Luck,
Jacob.