On 19 Feb 2013, at 1:40 PM, Rafal Bisingier wrote: > Hi, > > Or you could fix your application, to not do stupid things (like > generating millions of files in a single directory) in the first > place... ;-)
+1 > > > On 2013-02-19 at 12:10 CET > Paolo Aglialoro <[email protected]> wrote: > >> Or you could just use ZFS, XFS, whateverFS in a separate unix/linux box and >> go NFS on it, simulating a true external storage appliance :) >> >> >> On Tue, Feb 19, 2013 at 11:47 AM, MJ <[email protected]> wrote: >> >>> Which app are you running that is generating millions of tiny files in a >>> single directory? Regardless, in this case OpenBSD is not the right tool >>> for the job. You need either FreeBSD or a Solaris variant to handle this >>> problem because you need ZFS. >>> >>> >>> What limits does ZFS have? >>> --------------------------------------- >>> The limitations of ZFS are designed to be so large that they will never be >>> encountered in any practical operation. ZFS can store 16 Exabytes in each >>> storage pool, file system, file, or file attribute. ZFS can store billions >>> of names: files or directories in a directory, file systems in a file >>> system, or snapshots of a file system. ZFS can store trillions of items: >>> files in a file system, file systems, volumes, or snapshots in a pool. >>> >>> >>> I'm not sure why ZFS hasn't yet been ported to OpenBSD, but if it were >>> then that would pretty much eliminate the need for my one and only FreeBSD >>> box ;-) >>> >>> >>> >>> On Feb 19, 2013, at 2:35 AM, Keith <[email protected]> wrote: >>> >>>> Q. How do I make the default web folder /var/www/ capable of holding >>> millions of files (say 50GB worth of small 2kb-12kb files) so that I won't >>> get inode issues ? >>>> >>>> The problem is that my server has the default disk layout as I didn't >>> expect to have millions of files (I though they would be stored in the DB). >>> When I started the app it generated all the files and I got out of space >>> warnings. I tried moving the folder containing the files and making a >>> symlink back but that didn't work because nginx is in a chroot. >>>> >>>> The two option I think I have are. >>>> >>>> 1. Reinstall the OS and make a dedicated /var/www partition but how I >>> increase the inode limit I have no idea. >>>> 2. Make a new partition, format it, copy the files from the original >>> partition and swap them around and restart nginx. ( Do i run newfs with >>> some option to make more inodes ?) >>>> >>>> Thanks >>>> Keith. >> > > > > > -- > Greetings > Rafal Bisingier
