similar to: ext3 and lsdel

Hello friends, I am trying to learn recovering of file using debugfs. But even though i delete the file and run lsdel in debugfs it always gives me 0 deleted nodes found. Where am i making mistake?. [root at windce7 linux-2.4.32]# fdisk -l Disk /dev/hda: 40.0 GB, 40016019456 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot

Hello, I recently switched from 2.2 to 2.4 kernel. Each partition already contains a journal. I tried kernel-2.4.5-0.2.9 from RedHat Rawhide, where ext3/jbd is modularized. For the people who want to try this kernel, you first need to rebuild it, and enable CONFIG_JBD_DEBUG. This solves an unresolved symbol in jbd.o which prevents ext3 to load. (This issue will be solved in next RawHide) My

http://dovecot.org/rc/ Thought I'd still make one 0.99.10.x release now that mbox corruption problems are (hopefully) fixed. Please test, if no problems are found this will be the final 0.99.10.5. Changes since .4: + MySQL authentication, patch by Matthew Reimer - mbox: APPEND reversed given \Draft and \Deleted flags - mbox: "LF not found" errors happened sometimes when

One more bugfix since rc2: - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely Quite rare because we were lucky before :) And list of all the changes one more time: v0.99.10.5 2003-12-27 Timo Sirainen <tss at iki.fi> + MySQL authentication, patch by Matthew Reimer + --with-moduledir configure option - mbox: APPEND reversed given

Hello, I found the reason why "refuse options" is ignored on the server side. When then 5th argument (int val) in the poptOption struct is set to zero, the parsing function poptGetNextOpt() just continues with the next arg, without returning. So check_refuse_options() is simply not called in such cases. The attached patch makes "refuse options" work with checksum and

Hi All, Whenever an EXT3 partition is created some space is reserved for super-user, I used the mkfs.ext3 with option -m set to 0, but there is no effect it still reserve the space. How can i set the reserved-space to 0 or calculate the reserved-space in advance? Any suggestion/idea? Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I just found out, I deleted an important file, which was (of course) just downloaded to the computer from the digital camera, and deleted there. So, no backups. But when I tried to find the deleted INODE with debugfs and lsdel It said "no files deleted". Is this the normal behaviour? Is there a possibility of getting the data back? The kernel I use is 2.2.17-6 from the RH

I have a program which needs to compute squared Euclidean distance between two vectors million of times, which the Rprof shows is the bottleneck. I wondered if there is any faster way than my own simple function distance2 = function(x1, x2) { temp = x1-x2 sum(temp*temp) } I have searched the R-help archives and can not find anything except when the arguments are matrices. Thanks for any

Hi, I'm working with Prof. Zadok on versionfs, a stackable versioning file system. I face some problems with the unlink operation on ext3 with htree. On an unlink, I make a copy of the file (version/backup) and unlink the original file. But some files that have been unlinked are "linked back" to another file. For example, on deleting the file 'foo', the file itself is

Our Invoice posting routine (intensive harddrive io) freezes every few seconds to flush the cache. Reading this: https://listman.redhat.com/archives/ext3-users/2002-November/msg00070.html I decided to try: # elvtune -r 2048 -w 131072 /dev/sda # echo "90 500 0 0 600000 600000 95 20 0" >/proc/sys/vm/bdflush # run_post_routine # elvtune -r 128 -w 512 /dev/sda # echo "30 500 0 0

It's already mounted rw somewhere else. This enables the needs_recovery feature which prevents an ext2 mount. -Leslie -----Original Message----- From: Christopher J. PeBenito [mailto:pebenito@ieee.org] Sent: Tuesday, April 22, 2003 11:30 AM To: kuczynski, leslie Cc: 'ext3-users@redhat.com' Subject: Re: ext3 "noload" option to mount returning error in 2.4.9 & 2.4.18 s

Thank you to all who replied. I am very happy (for you guys anyway) to report that this was NOT infact caused by ext3, but rather a very very untimely memory failure that occured during my convertion from ext2 to ext3. It turned out that one of my PC2100 DDRs went south, and I'll be contacting Crucial to deal with that. Thanx again for all the help. benr. -----Original Message-----

Stelian Pop wrote: > I found out that a new version of ext3-2.4 was available from > the previous messages on this list, despite the fact that > no 'official' announce was given... I thought that the message, https://listman.redhat.com/pipermail/ext3-users/2001-July/000804.html , was the official announcement. BTW, no problems here with 0.9.0. 1 week and some hours of

postfix-users seems to be a subscription only list. I'd recommend incorporating TDMA <http://tdma.sf.net/> to allow for easy discussion by outsiders Andrew Morton (of ext3 fame) had sent this message to postfix-users list I am forwarding so that Wietse can hopefully provide the definitive answer to the question Andrew Morton/Stephen Tweedie seek ----- Forwarded message from Andrew

Hi all, i just had some enlightnening expirience. One of our servers died early this morning. When i rebooted it, it crashed again something like 5 seconds after finishing the boot, with the same oops message. Trying to figure out what is causing it i booted into single user mode and after some more crashes concluded that it is enough just to start postfix and the machine will crash within

Hi, Marc, Thanks for your help! a "ls -alFs" command shows the difference, Theodore Ts'o talked about it at https://listman.redhat.com/archives/ext3-users/2003-January/msg00008.html. Both File system and "/bin/ls" contains no bugs, my knowledge databse in my mind got lots of ""Bugs" instead. :) vista104 /0 > ls -alF total 211233264 drwxrwxr-t 5

In August I reported a problem with the sys_ftruncate call that caused me to reboot my machine. I didn't see any responses to it then on the ext3 list, and the problem is now recurring, so I thought I'd try again. I don't think I've rebooted since the last problem. In the last few days it hasn't taken as long as 17 hours, but it has sometimes taken unusual and uncomfortable

Version 1 was here: https://listman.redhat.com/archives/libguestfs/2023-February/030732.html (Ignore version 2 which had a mistake, this is version 3) Following Eric's suggestion here: https://listman.redhat.com/archives/libguestfs/2023-February/030746.html let's decrement the reference of py_array right after adding it to the args. (This works even if args fails to be built).

Version 1 was here: https://listman.redhat.com/archives/libguestfs/2023-February/030732.html Following Eric's suggestion here: https://listman.redhat.com/archives/libguestfs/2023-February/030746.html let's decrement the reference of py_array right after adding it to the args. (This works even if args fails to be built). However the other part of Eric's suggestion is wrong as

While messing around this script, I added one more tiny patch making wait-pnp log its output into the common log.txt file, as suggested by Richard here: https://listman.redhat.com/archives/libguestfs/2023-March/031023.html Discussion on v3: https://listman.redhat.com/archives/libguestfs/2023-March/031070.html v3 -> v4: * Remove unneeded line break from the script; * Add another small