Re: limits of files in directory (ReiserFS)
- From: Marcin N <nichu@xxxxxxxxxxx>
- Date: Sat, 19 Apr 2008 16:53:02 +0000 (UTC)
Dnia Fri, 18 Apr 2008 16:05:15 +0000, phil-news-nospam napisał(a):
On Fri, 18 Apr 2008 09:17:28 +0200 Marcin N <nichu@xxxxxxxxxxx> wrote:
| Those cache files doesn't use a lot of disk space but their amount is
| sometimes really huge - so backup isn't big but lasts long.
So the reading and processing of so many names is the issue. Configure your
backup software to skip over the directory with such names. If some software
has to find these, it has to be knowing where to look. That means there has
to be some kind of standard starting point name to look in. Put that in the
list of subdirectories not to back up. If your current backup software cannot
handle that, then raise that as an issue (the solution may be to improve that
software or switch to different software).
| And I want to make global solution - naming convention can be really
| different - so for this example I could change backup scripts - but for
| new ones with different names of course it wouldn't be valid any more.
What is the software that is using these files? Can no pattern be
determined from that?
| And I know about inodes limit but it's rather not good idea for me
| because other users would be punished and they could have problems with
| creating new files when someone else creates lots of files...
That sounds discriminatory, and without specifics. In other words, one user
is allowed to have many files, while another is not, yet you don't define
which is which, either?
But it sounds like your issue is users with 20000 files in ONE directory,
rather than users with 20000 files spread out among many directories.
Reiserfs handles both cases well. I'd look into your backup software if
it is a case like this, as the organization should not matter so much if
the software is well written.
| So reiser doesn't have such limits?
No. And I don't see that it ever will.
Backup software could do this just as well. As it reads names, it should
keep a count and test that against a configured limit (if one is configured).
OK I can configure my backup software to skip those files and for this case
it will work... it's not a problem. But what with next such accident when
user make cache directory but with different names of files? I have lots
of users and it's really difficult to monitor all accounts ...
Thank You anyway for responses
Regards
nichu
.
- Follow-Ups:
- Re: limits of files in directory (ReiserFS)
- From: phil-news-nospam
- Re: limits of files in directory (ReiserFS)
- References:
- limits of files in directory (ReiserFS)
- From: Marcin N
- Re: limits of files in directory (ReiserFS)
- From: h.stroph
- Re: limits of files in directory (ReiserFS)
- From: Marcin N
- Re: limits of files in directory (ReiserFS)
- From: Dances With Crows
- Re: limits of files in directory (ReiserFS)
- From: Keith Keller
- Re: limits of files in directory (ReiserFS)
- From: Marcin N
- Re: limits of files in directory (ReiserFS)
- From: phil-news-nospam
- limits of files in directory (ReiserFS)
- Prev by Date: Re: Problem with spaces in filenames in a script
- Next by Date: Re: tweak "write" message so that it includes the date
- Previous by thread: Re: limits of files in directory (ReiserFS)
- Next by thread: Re: limits of files in directory (ReiserFS)
- Index(es):
Relevant Pages
|