similar to: A few quick questions regarding the journal.

Hi, after trying to download the newest 2.4.6 patch (http://www.zip.com.au/~akpm/ext3-2.4-0.9.2-246.gz) I noticed that the file appears to be corrupt. gunzip: ext3-2.4-0.9.2-246.gz: unexpected end of file Tried a few times, on different machines. ( o> ///\ _\V_/_____________________________ [Sam]<mailto:sam@breakfree.com> http://www.xplo.org/ "finger

Hi, well I've deployed ext3 on two machines already and so far it does its job excellently at no (for me) noticable performance loss. I hope it gets incorporated into stock kernels by Linus soon. Anyways I've been hearing about ext3 supporting full-data journalling on a per-file basis but couldn't find any detailed info about it. Even tried grep'ing throught the source. How

Hi, I''ve just recently switched off my (lame) hardware firewall onto an old box running linux 2.4.18, iptables 1.2.6 and shorewall 1.2.9. I''m kinda new to linux firewalling myself but so far Shorewall has taken much work from me. While reading myself into iptables I saw that just recently something called ULOG (userspace logging) has been implemented in newer kernels and

Hi, I installed RH 7.1/e2fsprogs 1.22 and util-linux 2.11f on a box with a 3ware 6200 and 2 20GB IDE drives and then installed 2.4.7 and ext3 0.9.5 I unmounted all the filesystems except / and did a tune2fs -i 0 -c 0 -j <device> on all the remaining filesystems This created a journal with a hidden file. >From what I recollect, doing a tune2fs on a mounted fs creates .journal file. I

Hi, I tried to convert my root partition from an ext2 to ext3 fs using tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

On 2013-06-26, at 9:38 AM, Eric Sandeen wrote: > On 6/25/13 3:13 AM, Folkert van Heusden wrote: >> >> I have a system with an ext4 filesystem with its journal on an other >> device (an SSD). >> Now this SSD dropped of the sata bus so the filesystem went r/o. >> I would like to remove the journal but it says it can't because >> needs_check is set. >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I created all my ext3 partitions a while back, so the journal.dat file is visable. I'd like to remove them and use the new tune2fs functionality. Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and then remount as ext3? Or am I missing something? thanks! - -- Douglas J. Hunley (Linux User #174778)

On 6/27/13 3:57 AM, Folkert van Heusden wrote: > Eric, Andreas, > >>>> I have a system with an ext4 filesystem with its journal on an other >>>> device (an SSD). >>>> Now this SSD dropped of the sata bus so the filesystem went r/o. >>>> I would like to remove the journal but it says it can't because >>>> needs_check is set.

On Apr 29, 2004 14:15 +0200, David Mart?nez Moreno wrote: > Hello all. I'm writing to all the people in charge of ext3 fs > > Apr 29 12:21:21 arsinoe kernel: EXT3-fs error (device sda7): ext3_free_blocks: Freeing blocks not in datazone - block = 1071716394, count = 1 You need to run "e2fsck -f /dev/sda7" on the unmounted filesystem. There is some sort of corruption

I have been playing with external journals some more and thought I should share some experiences. I am running 2.4.16 with the ext3 patches from Andrew Morton and e2fsprogs 1.25 I have an ext3fs filesystem on an 8 drive RAID5 array and place the journal on a partition of the mirrored pair that I boot off (all drives SCSI). I have tried pulling the power cable and seeing what happens. I finally

Hi I was running few tests on the Ext3 filesystem having an external journal; basically trying to check recovery in crash scenarios. I started with simple scripts doing some filesystem operations on the ext3 partition and crashed the system with a direct poweroff. On reboot, I also corrupted the journal device by "dd"ing it out with blocks of zeroes. Now, when I try to mount the

>>>>> I have a system with an ext4 filesystem with its journal on an other >>>>> device (an SSD). >>>>> Now this SSD dropped of the sata bus so the filesystem went r/o. >>>>> I would like to remove the journal but it says it can't because >>>>> needs_check is set. >>>> >>>> What does it actually

Hi there, I started getting errors on one of my 2 drives, so I got a warranty one. Then I made an exact copy of the failing one onto the new one with dd, and swapped them. I ran fsck on all the affected partitions, and things looked good. Then I started using the striped RAID device (ext3) which had some minor data loss (mostly under big files), and I got the problems with the journal. The

Eric, Andreas, >>> I have a system with an ext4 filesystem with its journal on an other >>> device (an SSD). >>> Now this SSD dropped of the sata bus so the filesystem went r/o. >>> I would like to remove the journal but it says it can't because >>> needs_check is set. >> >> What does it actually say? there is no needs_check flag

Hopefully, someone can tell me if this is OK. I recently had a problem with my system and had to do a complete restore. Fortunately, I had made a full backup just the day before. My filesystems are Ext3 (why else would I be posting this here?). :) Anyway, when I originally changed my filesystems from Ext2 to Ext3, I did while they were still mounted. As a result, the journal file was visible.

Hi I'm experiencing some problems on a harddisk (it has crashed for no known reason), and in pursuit of getting some of the data out of the disk I'm learning to use the e2fs progs package. Origianlly I used version 1.38, but after experiencing segfaults in e2fsck -which now is solved, I upgraded to 1.39, but now I have hit another problem (on another partition): The partition was

My UPS failed and my server took an 'unscheduled outage' a few weeks ago. The only casualty appears to be a volume I used for backup. I usually maintain data on multiple hard disks, but in this case I errantly had some data (of marginal value) on this file system. At this point, the data is not worth enough for me to send the drive out for data recovery, but it's worth enough to

Hello On root Partition is .journal visible . On all other Partitions is invisible. At which way I can move it manually to a hiden inode? I have delete with chattr -i /.journal rm -f /.journal and installed ext3 with tune2fs -j /dev/hdb1 And /.journal is again visible! -- MfG / With best Regards Rusmir Duško Registered Linux user: #130654 http://counter.li.org

Hello, I recently implemented ext3 using tune2fs -j /dev/hda1, and have been using it successfully for a while. However the .journal file is huge and growing on my limited amount of disk space. How can I rotate or re-initialize the file, preferably without rebooting, on a daily/weekly basis? Regards, Dan Barber Mojolin --------------- Mojolin: Linux, Unix and Embedded Jobs and Resumes.