similar to: RH 6.2 + VA Linux Enhancements (includes ext3 0.5b) Problem

Hi, I have uploaded ext3-0.0.5b.tar.gz to ftp.*.kernel.org:/pub/linux/kernel/people/sct/fs/ext3/test/ and ftp.uk.linux.org:/pub/linux/sct/fs/jfs/test/ New in this release is a functionally complete implementation of metadata-only journaling: data writes will no longer have to be written to the journal. Journaling still imposes some extra serialisation points between interacting processes, so

Hi all, OK, here is ext3-0.0.5e. Changes since 5d are summarised below. The major changes are the barrier support: this infrastructure should be sufficient to allow the snapshotting interface which LVM is wanting for ext3. The journal initialisation fix will also help people adding ext3 to an existing filesystem. Look for ext3-0.0.5e.tar.gz on:

Hello wonderful rsync I have a little problem... I sync a file system with this command: rsync -avzAXH --filter="-r *.jpg *.opml *.opml.backup *.m3u" --delete-after --exclude=MP3s /home/Music/ /misc/bigdisk.mythtv.lan/Music /misc/bigdisk.mythtv.lan is an nfs mount mounted by autofs. In /etc/auto.misc I have for /misc/bigdisk.mythtv.lan: bigdisk.mythtv.lan -fstype=nfs4

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

Hi all, ext3-0.0.5c is now up at: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ The most important part of this release is the e2fsprogs: e2fsck now supports the journal changes for metadata-only journaling. Ted, I've changed around the use of jfs* include files in e2fsprogs quite heavily here. In each build directory --- the lib/ext2fs

Hi, I operate a distributed replicated (1:2) setup that looks like this: server1:bigdisk,server1:smalldisk,server2:bigdisk,server2:smalldisk replica sets are bigdisk-bigdisk and smalldisk-smalldisk. This setup will be extended by another set of four bricks (same setup) within the next few days, and I could make those into another volume entirely, but I'd prefer not to, leaving me with more

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there some limit on the size of a file system which can be shared via samba? I'm trying to set up a file server with a 100GB shared partition and it doesn't want to work. I'm running Fedora Core 4, and Samba Version 3.0.14a-2. The output from testparm looks like this: [root@stitch samba]# testparm Load smb config files from

(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

-----Original Message----- From: 박노희 [mailto:nohhee@turbolinuxsystems.com] Sent: Tuesday, July 31, 2001 1:35 PM To: 'ext3-users-admin@redhat.com' Subject: ext3 problem? Please give me advice about the following problem. A few days ago, I lost some of oracle DB data on my server. My server was running Oracle DB and HA(high availability) server for web service. The filesystem was ext3,

Ok, so I''m obviously doing something wrong here. This is running puppet 0.22.2 on a centos 4 update 4 box. When I try running this test - mount { bigdisk: ensure => mounted, device => ''bigserver:/bigdisk'', fstype => nfs, name => ''/bigdisk'', dump => "0", pass => "0", options =>

Hopefully this is a simple issue or just my ignorance on the results returned by "df -k" but can anyone explain why the available block is 0 if total 1k-blocks - Used is greater than 0? #df -k /ems/bigdisk/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg0-bigdisk 397367512 383562960 0 100% /<name> Filesystem volume

hello all, I am trying to expand my /var file system which resides on a logical volume. I successfully issued the lvextend command. However when I try to issue the ext2online command I receive a return code of 3 which the man pages indicates: ext2online /var ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2online: group 0, block 7 not reserved ext2online: unable to resize

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 13:05, Rick Sivernell babbled: > Doug > > Educate me please. What is the diff between ext2 & 3. I am using reiserfs > now and do like it. But I do like to have the stuff going, if I can. Be warned, I know nothing about reiserfs other than what I've read. short version: ext3 is a further development of

Hi, I am trying out ext3 with an external journal (on a battery backed RAM card). I use data=journal, and sync nfs writes go nice and fast :-) But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it

[ If this is explained somewhere else (HOWTO or FAQ), please give me a pointer. ] Is there any way to mix loop-device (and in particular) loop-AES and ext3 together in data journaling mode? Ie. bottom -> to -> top ext3 - loop-AES - ext3 raw - loop-AES - ext3 Or am I shooting myself to leg, I am? BR, Jani -- Jani Averbach

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

When trying to build ext3 as a module, I get the follwing errors during the kernel link: /usr/bin/kgcc -D__KERNEL__ -I/home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/include -c -o dummy_sym.o dummy_sym.c ld -m elf_i386 -T /home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_t ask.o -Map map

Hi Stephen, could you give us an idea, when we could expect the patch for the 2.4-series kernels? Do you have a 'roadmap' here or are you waiting here for the 'complete' kernel-API for the journaling filesystems? thanks, Joachim -- Joachim Kunze Alte Marktstrasse 16 Tel.: +49-7042-830006 D-71665 Horrheim Fax: +49-7042-830006 Germany eMail:

Hi I am running a PC under Linux SuSE 7.2 with kernel 2.4.18, self compiled. I changed some days ago the partition of my second HD from ext2 to ext3 with the help of tune2fs -j /dev/hdb2 and everything was running OK. Today, I had a problem with a frozen display and I had to reboot the box cold. During the corresponding forced check I got the following messages: Quote --------- /dev/hdb2: reading

One of our users here got the following with an ext3 0.0.6b: # debugfs /dev/hda3 debugfs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 /dev/hda3: Bad magic number in super-block while opening filesystem debugfs: Does debugfs need updating? b.