search for: evilninja

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, after upgrading to samba 3.0.8 (debian/unstable, i386) i too encounter similar problems as reported here: http://lists.samba.org/archive/samba/2004-November/095567.html upon logoff from a win2k(sp4) client, the profile cannot be saved and the samba logfile from the client (prinz) gives: [2004/11/26 17:57:06, 2]

Let me preface this by saying "Yes, I know *nix filesystems don't need to worry about fragmentation". That said, is there a way to check the overall level of fragmentation of a live ext3 filesystem? I know about filefrag, but that's for specific files. And I think e2fsck tells you, but only if you take the filesystem offline for the scan. Is there anything that will give

...with 1.30-WIP gives HTREE errors again. please give me a hint on what to do. in daily usage i got no errors and no anormalities in using the fs but and don't wanna wake up one day and see everything screwed up. Thanks in advance, Christian. -- ############ Christian ############## ######## evilninja@gmx.net ########## #####################################

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No-one out there who can give me any tips for this? (Then the space to do experiments will finally be used in other ways. And I hope this mail won't be consired to impolite...) On Mon, 6 Dec 2004 15:23:15 +0100 Milan Holz?pfel <lists at mjh.name> wrote: > Hello, > > I got an IDE-drive which decided to get broken. Part of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, today i re-organized my data, lots of "mv" and "cp". then, upon unmounting a ext3 partition the following was shown on the console: (the leading "Mar 22 02:40:04 sheep kernel:" is cut here) - ------------------------------- ~ sb orphan head is 940994 ~ sb_info orphan list: ~ inode sdd4:940994 at cf852874: mode

Dear All Problem with ext3 fs on 3ware 9500S controller: Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #145998372: rec_len is smaller than minim al - offset=0, inode=0, rec_len=0, name_len=0 Dec 7 05:59:50 stams kernel: Aborting journal on device sda1. Dec 7 05:59:50 stams kernel: ext3_abort called. Dec 7 05:59:50 stams kernel: EXT3-fs

Hi, By running some scripts on our target system for a while, I lost all means of access to the system. It seems that the kernel is crashed with the following error message: Assertion failure in do_get_write_access() at transaction.c:731: "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)" Oops: Exception in kernel mode, sig: 4 We are currently running Linux version

Hello, Yesterday evening this box crashed and, for once, ext3 was not able to recover automatically. There was an "unexpected inconsistency inode xxxxx has imagic flag set" error and the system would not boot. I fscked from my rescue disk and I guess 20 or 30 errors were fixed by me just selecting "y" at the prompt. The system then booted and, so far as I can tell, the only

(please reply on-list, so everybody can comment/help) Matt, thanks for the details, but apart from mount-option tuning and dir_index (which you've already enabled), I dunno why ls(1) would take *hours* to stat ~1M files... out of curiosity: are you able to try a newer kernel? does it change anything? Christian. ---------- Forwarded message ---------- The dir_index was enabled during

oh, I am using: $ quota -V Quota utilities version 3.13. Compiled with RPC and EXT2_DIRECT Bugs to mvw at planets.elm.net, jack at suse.cz are there any special versions out there for v2 quotas? thanks, Christian. ------------- Hi list, having used ext2/3 for years now I have to admit that I've never dealt with filesystem quotas yet. But now I want to use them and I'm rather puzzled

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 [cc'ing 4 mailing lists, please reply to *one* list only!] hi, every now and then i'm running some benchmarks on filesystems i really use...here are the results: http://nerdbynature.de/bench/prinz64/2.6.14-rc2-mm2/bonnie.html http://nerdbynature.de/bench/prinz64/2.6.14-rc2-mm2/ may it be of some help.... thanks, Christian. PS:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [!! i've Cc'ed several fs lists, please remove when when replying !!] hi all, from time to time i do some benchmarks for several filesystems and several crypto-algorithms too, details here: http://nerdbynature.de/bench/ latest results here: http://nerdbynature.de/bench/prinz/2.6.12-rc3-mm2/bonnie.html

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [cc'ing 4 mailing lists, please reply to *one* list only!] hi, i was about to set up a new fs for my desktop machine and i could not decide which fs it should be. i've written a wrapper script for some benchmarks before, but it was not really good. i tried to rewrite it and so, here are the results: http://nerdbynature.de/bench/

boy, if you really care about your problem, *USE* ext3-users: > oh, and please respond on-list, perhaps other ppl are curious > about some details too ;) really. Tobias Amon schrieb: > Hi, > > I use e2fsprogs version 1.5.2 (I think) http://e2fsprogs.sourceforge.net/ exists, latest version is 1.35. > I got another solution. Yast, which came with Suse > is not able to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, a good friend of mine had some trouble with his fs yesterday. i have some details now and wonder if you have some thoughts on it, even it may turn out not to be an ext3 issue at all. sorry, the post is a bit too long: the ext3 fs was running for several months now on a RAID controller. due to a user error, the RAID controller decided to rebuild