similar to: Subject: Re: dual-ported raid

Hi, I have a dual-ported raid controller which allows two computers to connect to the same ext3 filesystem. I never mount both systems read-write at the same time. What I would like to do is use one normally, and mount the second system read-only to perform backups and to rsync the filesystem to another filesystem. When it's mounted read-write from another system, will mounting the same

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote: >> I am reporting this on the advice of the Fedora Users Mailing List Member. >> >> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. >> >> I am reporting this per

>From nfs-admin@lists.sourceforge.net Thu Feb 1 03:51:36 2001 >Return-Path: <nfs-admin@lists.sourceforge.net> Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id DAA11596 for <jareth@camelot.co.jp>; Thu, 1 Feb 2001 03:51:35 +0900 X-Authentication-Warning:

After a rather severe hard boot, my machine refuses to mount homes, which are on an ext3 partition. Here is the error i get while mounting... # mount /dev/sdc1 EXT3-fs: invalid journal inode EXT3-fs: get root inode failed mount: wrong fs type, bad option, bad superblock on /dev/sdc1, or too many mounted filesystems However I am able to mount it as ext2 and continue. I am using ext3-0.0.6b on

Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

Had two scsi hard drives. One went bad. The bad one had lilo in the MBR. Removed the drive. Then used the Mandrake install cd to boot into rescue mode. Was able to mount all filesystems within rescue mode on remaining hard drive (HD went from sdb to sda). Only glitch was that I could not mount root filesystem as type ext3 -- had to mount as ext2. Modified the lilo.conf file and ran lilo with new

Hello, Many warm thank yous to Bill Rugolsky Jr. and Stephen Tweedie for their help on this one. Both pointed out that since the file system is journaled, if the primary box (nas1) were to crash, the secondary box should mount the ext3 file system without any problems. Depending on the nature of the journal (metadata journaling and/or data journaling), we may have little or no data loss. Bill

Hi Everyone, I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error dmesg reports: EXT3-fs: invalid journal inode. I tried to run e2fsck and it failed (The output can be seen below). If anyone has any suggestions on how I can restore

Hello, Setup: ------ I have two RedHat 7.2 (2.4.9-31) boxes that are attached to one external RAID unit. Both boxes are able to see the RAID unit as /dev/sdb1, but only one box mounts (cat /proc/mounts yields: /dev/sdb1 /nas ext3 rw 0 0) the unit at any give time. The other box listens, via heartbeat (linux-ha), waiting to mount the RAID unit, should it''s sibling crash (actually,

Hi, After mounting -t ext2 an ext3 partition, working with, do I have to recreate .journal when I remount the partition as ext3 ? Thanks ! Liu

Consider this section: http://www.tldp.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.14 I have not done this before and I'm leary about Step 11 which is resizing the filesystem after doing a mkraid command. This howto lacks any ext3 documentation. Some questions I have are: 1. Should I convert back to ext2 on all my filesystems before I do a mkraid? 2. If I leave the system at ext3, will the

On Tue, 24 Jun 2003 ext3-users-request@redhat.com wrote : >Send Ext3-users mailing list submissions to > ext3-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request@redhat.com > >You can reach the person

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, just wondering... if i upgrade my kernel + ext3 patch, do i have to recreate the journal? if so (or if not) how do i recreate it? i tried to delete the .journal, reboot and mounting everything as ext2 and do a tune2fs -j /dev/hdxx but it say "The filesystem already has a journal." Thanks, Mark -----BEGIN PGP

Hi guys'n'girls, I think my question is : How can I tell a redhat 2.4.x kernel (via grub or LILO command-line parameters) that the root filesystem is ext2 and not ext3 ? I thought it would just look in /etc/fstab, but presumably it needs to know what fstype the root is before mounting it; the words 'chicken' and egg' spring to mind. Or does some initrd jggerypokery go on?

Hi I have a Firewire connected Micronet 1.5TB RAID with a single large ext3 filesystem on one partition on a dual Xeon system. I am checking out from an extremely large cvs repository (don't ask) to this drive over the course of many days, and intermittently I get bad blocks and the filesystem goes read-only. This is not related to any power failure or anything similar. The RAID is currently

Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when

>From nfs-admin@lists.sourceforge.net Wed Jan 31 09:21:55 2001 >Return-Path: <nfs-admin@lists.sourceforge.net> Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA03106 for <jareth@camelot.co.jp>; Wed, 31 Jan 2001 09:21:53 +0900 X-Authentication-Warning:

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode,

I have a raid5 array on my web server for which I am currently considering a move to ext3. I want to use an external journal to improve performance. Since the external journal would reside on a drive that is not participating in the raid array, I'm wondering what the behavior of an ext3 filesystem is should the device an external journal is on should fail. If it reverts to ext2