All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chet Hosey <chet@colo.tr0n.com>
To: reiserfs-list@namesys.com
Subject: Re: REISERFS_MAX_NAME and ENAMETOOLONG
Date: Mon, 22 Aug 2005 09:03:37 -0400	[thread overview]
Message-ID: <20050822130337.GA10132@sx-hosting.com> (raw)
In-Reply-To: <43099E14.7060902@baldauf.org>

On Mon, Aug 22, 2005 at 11:42:44AM +0200, Xu?n Baldauf wrote:
> Hello,
> 
> when downloading something from java.sun.com (e.g. 
> http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&PartDetailId=jdk-1.5.0-doc-oth-JPR&SiteId=JSC&TransactionId=noreg 
> ), very long URLs are encountered. When trying to download using "wget", 
> wget tries to open a file with those long filenames, and fails with 
> ENAMETOOLONG (File name too long).
> 
> I think that the limit is due to the REISERFS_MAX_NAME macro 
> (http://lxr.linux.no/source/include/linux/reiserfs_fs.h?v=2.6.10#L1107), 
> which currently resolves to "255" (which supposedly means 255 bytes).
> 
> Is it safe to change REISERFS_MAX_NAME to something larger, or does this 
> change the disk layout in an unexpected or incompatible way?
> 
> Thanks,
> 
> Xu?n Baldauf.
> 

I'm sure you've investigated this, but you might also consider the -O
option to wget -- it probably isn't quite what you're looking for if you
are fetching multiple files (such as with --mirror), but when fetching
one file at a time it's quite a bit less drastic than recompiling the
kernel and putting extremely long file names on disk.

Chet

  parent reply	other threads:[~2005-08-22 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  9:42 REISERFS_MAX_NAME and ENAMETOOLONG Xuân Baldauf
2005-08-22  9:50 ` Vladimir V. Saveliev
2005-08-30  7:01   ` Jeff Mahoney
2005-08-30  8:33     ` Xuân Baldauf
2005-08-22 13:03 ` Chet Hosey [this message]
2005-08-22 14:13 ` michael chang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050822130337.GA10132@sx-hosting.com \
    --to=chet@colo.tr0n.com \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.