search for: bothi

----- Original Message ----- From: "Bodo Thiesen" <bothie@gmx.de> To: <ext3-users@redhat.com> Sent: Monday, August 25, 2014 8:15 PM Subject: Re: filesystem > Hello Bill. [snip] > You're trying to understand what exactly? From the user point of view, > dir_index just makes directory accesses on very big directories faster. > When...

...e is now 1237669144) [2009/03/21 22:59:05, 5] libads/ldap_utils.c:ads_do_search_retry_internal(64) Search for (|(attributeId=1.3.6.1.1.1.1.0)(attributeId=1.3.6.1.1.1.1.1)(attributeId =1.3.6.1.1.1.1.3)(attributeId=1.3.6.1.1.1.1.4)(attributeId=1.3.6.1.1.1.1 .2)) in <CN=Schema,CN=Configuration,DC=bothi,DC=fi> gave 0 replies [2009/03/21 22:59:05, 3] libads/ldap_schema.c:ads_check_posix_schema_mapping(243) ads_check_posix_schema_mapping: failed NT_STATUS_NONE_MAPPED [2009/03/21 22:59:05, 2] nsswitch/idmap_ad.c:ad_idmap_cached_connection(152) ad_idmap_cached_connection: Failed to obtain schem...

Hello Bill again. Two things. First. I read this mailing list, so no need to send answers to me personally in copy. Second. I guessed it already, but now it got really obvious, that you didn't do your homework. Please search for your questions in your favorite search engine first. Yes, I know, that there is not much easy to understand information on ext2 (in all flavours) out there, but

On Oct 16, 2014, at 10:25 AM, Bodo Thiesen <bothie@gmx.de> wrote: > * Andreas Dilger <adilger@dilger.ca> hat geschrieben: > >> You can see in the ext4 superblock the amount of data that has been >> written to a filesystem over its lifetime: >> >> Note that this number isn't wholly accurate, but rather a...

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > You can see in the ext4 superblock the amount of data that has been > written to a filesystem over its lifetime: > > Note that this number isn't wholly accurate, but rather a guideline. Is is more like a completely bogus value at best: # LANG=C df -h / | grep root /dev/root 3.7T 3.6T 73G 99% / # grep [0-9]

* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > I hope this is the right list. I have created an ext2 filesystem and > removed the dir_index feature. I don't know if this kind of experimentation > is going to help me learn something about filesystems or not. Well what is > dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I >

I hope this is the right list. I have created an ext2 filesystem and removed the dir_index feature. I don't know if this kind of experimentation is going to help me learn something about filesystems or not. Well what is dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I remove? Htree. I guess it can always be put back and it's on an experimental filesystem.

* Keith Keller <kkeller@wombat.san-francisco.ca.us> hat geschrieben: Hi Keith > I have a very similar second server which has undergone a similar chain > of events, an initial ~2.5tb fs followed by a resize later. I believe > that it has been fsck'd since the resize (but don't quote me on that). > Am I likely to run into this issue with this fs? And if I do, what >

* "Theodore Ts'o" <tytso@mit.edu> hat geschrieben: Hi Theodore. > That being said, it's pretty clear that portions of the inode table > and block group descriptor was badly corrupted. [...] Keith is not the first one with problems of this class and he will probably not be the last one. He later told us, that at first, mounting the file system still worked. And that

Hello. After reading some mails from mailing list archives and other sources, ext3 seems to having troubles in deleting files w/o destroying the data neccessary to undelete them. Ok, I know what journaling means, and in any way, the ext3 fs driver needs to keep track of which blocks have actually been marked as being free. But now my question: Who say, that this information must be stored in

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > The "lifetime writes" value has not been around forever, so if the > filesystem was originally created and populated on an older kernel > (e.g. using ext3) it would not contain a record of those writes. It was created as stable ext4 in the first place. So only if there was a stable ext4 release which didn't