From: Andreas Dilger <adilger@turbolinux.com>
To: John R Lenton <john@grulic.org.ar>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>
Subject: Re: ln -l says symlink has size 281474976710666
Date: Tue, 13 Mar 2001 22:58:08 -0700 (MST) [thread overview]
Message-ID: <200103140558.f2E5w8P06685@webber.adilger.int> (raw)
In-Reply-To: <20010314022236.D18554@grulic.org.ar> from John R Lenton at "Mar 14, 2001 02:22:36 am"
John Lenton writes:
> burocracia:~# debugfs /dev/hda2
> debugfs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> debugfs: stat <404176>
> Inode: 404176 Type: symlink Mode: 0777 Flags: 0x0 Generation: 2457884131
> User: 0 Group: 0 Size: 281474976710666
> Fast_link_dest: imlib-base
> debugfs: stat <404192>
> Inode: 404192 Type: symlink Mode: 0777 Flags: 0x0 Generation: 1796859698
> User: 0 Group: 0 Size: 281474976710669
> Fast_link_dest: /proc/self/fd
So it is garbage in the "i_size_high" field (=i_dir_acl) in the inode.
> this is after an e2fsck, after a reboot, after restart. Nothing
> in the logs. The inodes are as old as the system, which isn't all
> that old (circa the first release with reiserfs).
Luckily, after the symlink is created it ignores the size, and only uses
the i_blocks count to determine if the symlink is stored in the inode
itself or in another block (the fast symlink will be NUL terminated).
It could well have been corruption from a long time ago, and only with
2.4.x and LFS you have noticed it.
Probably e2fsck needs to be updated to check for and fix this problem -
it is impossible for a symlink to be larger than a single block, so
the i_size_high field should always be zero.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-14 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 6:35 John R Lenton
2001-03-13 21:47 ` Andreas Dilger
2001-03-14 5:22 ` John R Lenton
2001-03-14 5:58 ` Andreas Dilger [this message]
2001-03-14 9:38 ` Xavier Bestel
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=200103140558.f2E5w8P06685@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®