similar to: Ext3 emergency recovery

Hello, We have run and stopped by chance command "fsck -y" on one of our raid disks (with ext3 file system). After that we have found that SOME files disappeared (they are not seen in the directories where they have been before). The data are extremely important and contain a lot of programs, scripts for some data analysis and very hard to recover by hands. I have run ''fsck

Having just spent a day trying to recover a deleted ext3 file for a friend, I'm wondering about this way of maintining undelete information in ext3, like is done for ext2: The last step in the deletion process would be to put back the (previously zeroed) block pointers. Since it gets logged to the journal, I _think_ that this should be safe. The worst that would happen is that, if the plug

We are running a benchmark that does single threaded 512 KB writes to a LUN on a CLARiiON storage array. The dual Xeon host (Dell 2650) with 4 GB of memory runs RHEL 4U3 We measured the write bandwidth for writes to the block device corresponding to the lun (e.g. /dev/sdb), a file in an ext2 filesystem and to a file in an ext3 file system. Write b/w for 512 KB writes Block device 312 MBps Ext2

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

Hi I have a problem with lm and predict I have us [1] 2789.53 3128.43 3255.03 3536.68 3933.18 4220.25 4462.83 4739.48 [9] 5103.75 5484.35 5803.08 5995.93 6337.75 6657.40 7072.23 7397.65 [17] 7816.83 8304.33 8746.98 9268.43 9816.98 10127.95 10469.60 10960.75 [25] 11685.93 12433.93 13194.70 13843.83 us.p [1] 227.62 229.92 232.13 234.25 236.31 238.42 240.59 242.75 244.97

Hi! I have made some extensions to debugfs to undelete or recover files from a damaged ext3 file system. Salvage or undelete files of damaged ext2/ext3 file systems debugfs salvage command can be used to salvage files from a damaged ext3 or ext2 file system. The code is alpha, so use at your own risk. the usage is: salvage first-block count-blocks Salvage tries to salvage files found in

Hi I have written a small introduction to newbies in Danish on ssh and friends. Now some people are questioning my advice and I think they have a point. I am advocating people to use DSA-keys and a config file with this: Protocol 2 ForwardAgent yes ForwardX11 yes Compression yes CompressionLevel 9 and running ssh-agent and ssh-add, and then loggin in without giving keys. One

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

Hi I got a strange error, happening on two of my ext3 partitions. What can be wrong? And why does e2fsck error out, instead of displaying an error message? Best regards keld fsck /dev/hda6 fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning... fsck.ext3 for device /dev/hda6 exited with signal 11. also From my dmesg: <1>general protection fault: e7a8 [#3] Modules linked in:

I am having some trouble with an ext3 partition, getting the following error when i go to fsck the partition: fsck.ext3: Bad mgic number in superblock while opening /dev/sda2 I tried the -b 8193 option, to no avail. Can anyone out there help me recover this partition?? ---- Michael B. Weiner Senior Systems Administrator/WebOps AmericanGreetings.com Three American Road, Cleveland, OH 44144

I sent to samba list, with the wrong e-mail account, so it never made it... Any help with this is appreciated. Barry Smoke District Network Administrator Bryant Public Schools -----Forwarded Message----- > From: Steve Langasek <vorlon@dodds.net> > To: k12osn@redhat.com > Cc: lrlug-discuss@lrlug.org, samba@lists.samba.org > Subject: [Samba] Re: [K12OSN] Re:

Hi I would like to sum a number of time series, some of them having NA's Standard action is here that if I sum a value with a NA, then the result is NA. I would like it to just keep the value. I then try to: a = NA; if (a == NA) { a = 0} just to try it out, but it says Error in if (a == NA) { : missing value where TRUE/FALSE needed What is wrong, and can I do it smarter? I looked at

Hello, I got this message when exiting qemu: [11266.262154] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318015 [11266.276897] Aborting journal on device hda. [11266.283815] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318016 [11266.293567] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318017

[Re-sending to the ext3 list, with minor edits] I'm in the process of fixing errors generated by the Coverity tool on the Linux kernel, and I would like your comment on a set of problems reported in ext3. The main issue reported is not checking the return code of ext3_journal_get_write_access() in various places. I would like to know if there should be error handling in these cases. The

Hi Everyone, I am desperately looking for some help from community, I am having issues with one of the xen server hosts and they can not be recovered from Emergency mode as they are not able to talk to pool master. I am rebuilding server every time i came across this situation, there have to better way to recover XEN host from emergency mode. I am using Citrix XenServer 5.6 on Dell hardware, Is

Hi, I accidentally issued "mkswap" on a used ext3 fs partition (~30G) :-/ I have analyzed the behaviour of mkswap using two test files and it appears to only change "some" bytes: --8<-- --- swap2.xxd 2005-07-04 21:00:10.157261360 +0200 +++ swap1.xxd 2005-07-04 21:00:01.894517488 +0200 @@ -62,7 +62,7 @@ 00003d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................

Have you had any luck with recoverin ghte ext3 partition? I have the same problem and I have found no literature on the web whatsoever... Please if you have found a solution, let the world know... -Daniele