This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/226] [RFC] d_type is always set to "0"
- From: "jakub at redhat dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 18 Jun 2004 12:17:31 -0000
- Subject: [Bug libc/226] [RFC] d_type is always set to "0"
- References: <20040617225924.226.cbou@mail.ru>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From jakub at redhat dot com 2004-06-18 12:17 -------
{d_ino=587521, d_off=64, d_reclen=20, d_name="local"}
is a proof that the kernel provides the d_type information to userland, just
it is apparently zero.
If the kernel did not provide the d_type information, d_reclen for
strlen (d_name) == 5 would be 16.
(Hint: d_ino and d_off are both 4 bytes long, d_reclen 2 bytes, then d_name,
it's zero terminating byte and then d_type (not shown in strace output).
So I guess you need to look why your ext2 doesn't provide that information.
Maybe it was built by very old mke2fs or set on purpose for 2.2 (or was it 2.0)
kernel compatibility or something like that.
If you do debugfs /dev/whatever_is_your_fs_mounted_on
and do stats, does it print filetype among filesystem features? Mine looks like:
Filesystem features: has_journal dir_index filetype needs_recovery
sparse_super
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
http://sources.redhat.com/bugzilla/show_bug.cgi?id=226
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.