similar to: 2.2.19+ext3 or 2.4.1x+ext3 ?

rsync-2.4.6-2mdk I ran an rsync into a file system that filled up. I got no error message out of rsync - it just stopped and exited sliently. I stuck an fprintf into the receiving code and verified that the proper error was being generated - it just never gets printed by the rsync sending process. I submitted a bug report about it; but, I can't believe that other people haven't had

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

I'm getting only partial iso8859-1 translation from an smbfs mount from my Win98SE machine. The smbfs mounted file system shows most lower-case accented characters fine; but, it substitutes underscores for most of the upper-case accented characters (and a few lower-case ones too): # uname -a Linux elm 2.4.18-8.1mdkian3 #7 Sat Aug 17 15:19:44 EDT 2002 i686 unknown (Mandrake 8.2 Linux with all

I'm trying to pick a kernel for ext3. Looking at the web page (http://www.zip.com.au/~akpm/linux/ext3/), I see little that clues me in to the fact that "most" of ext3 is already in (some|most|all) of the 2.4 series kernels. Am I correct that most of the patches listed on the web page now are actually bug fixes to the existing ext3 code, as opposed to previous patches that actually

Hi, I seem to have a problem with compiling the kernel 2.4.13 on redhat 7.2? It would compile fine but have errors about ext3 support on reboot. I download ext3-2.4-0.9.13-2413.gz to my linux machine to enable it be useful with ext3 support but when I try to gunzip it with the instructions gunzip < ~/ext3-2.4-0.9.13-2413.gz | patch -p1 i get gunzip: stdin: not in gzip format I get an

I just upgraded to kernel 2.4.14 and applied the ext3 patch ext3-2.4-0.9.15-2414.gz. It appears (to me) that the patch breaks the loop block device module (loop.o). The problem is that the call to deactivate_page is unresolved. The routine used to be defined in swap.c. It looks like it no longer exists in 2.4.14. I'm not a kernel programmer so if I'm mistaken, sorry. I do get an

When I try to compile e2fsprogs-1.24a I receive the following snippet: tillarium:/home/tilleyrw/downloads/ext3 Files/e2fsprogs-1.24a# mkdir build;cd build tillarium:/home/tilleyrw/downloads/ext3 Files/e2fsprogs-1.24a/build# ../configure <<SNIP>> ./mk_cmds: Files/e2fsprogs-1.24a/lib/ss: No such file or directory mk_cmds: Couldn't find mk_cmds's template files. make[2]: ***

Hi all, ext3-0.0.7a is now out, at the usual places: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and propagating now from ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ This fixes one major bug in ext3 recovery for metadata-only journaling. Because recovery can also happen in e2fsck, users should also upgrade to at least e2fsprogs-1.21-WIP-0601 (also provided at the above ftp sites).

The latest errata kernel-2.2.19-6.2.7.src.rpm contains old patches linux-2.2.17-ext3.patch linux-2.2.17-kdb+ext3.patch Is there somewhere a 0.0.7a version of the above that will patch cleanly in the errata kernel (considering all the other patches that get applied before ext3)? I read about ftp://ftp.clusterfilesystem.com/pub/ext3 but when I do $ rpm -qpl

Hi, i am seeing something interesting since the upgrade to 2.2.19/0.0.7a - I am experimenting with the am930 wireless driver and i am crashing on module exit. Everytime i reboot afterwards the var fs on /dev/hda8 is inconsistent [...] Checking all file systems... Parallelizing fsck version 1.21-WIP (01-Jun-2001) /dev/hda7: recovering journal /dev/hda7: clean, 39160/320640 files, 354596/640702

hi, is this rpms differ from redhat's rawhide 2.4.5 kernel which seems to contain ext3. so my question that your rpm contain different ext3 than rh's rpm? or I can simple use rh's rawhide rpms? thanks. yours. ps. please reply to my private address to since I'm not on the list. thanks. > Hi, > > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.

In the Red Hat Linux spec file for the 2.2.19 kernel, there is a note not to enable ext3 and LFS at the same time. I'm wondering whether this is an old note, and that it is safe to use ext3 0.0.7a on a system with LFS enabled, or if there are still issues with it. I'm aware that 0.0.7a is a really old version, and 2.2 isn't the most modern kernel, but it is what I have to work with.

Hi everyone, I've been reading this mailing list once in a while and I have seen that there are quite a few bugs that were resolved since EXT 0.0.7a. I was wondering if using 0.0.7a with kernel 2.2.19 is dangerous or ok because I have had some corrupted files once in a while (using compact flash disk CF on IDE bus). 0.0.7a is the only patch available for kernel 2.2.19 to my knowledge are

We have a machine that is trying its darndest to house a linux kernel cvs repository. The machine is a dual 733mhz p3 netfinity of some kind. 512M of mem. Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda1 16484504 4015876 11631240 26% / /dev/sda2 31079 3199 26276 11% /boot /dev/sdb2 16516084 32828 15644264 1%

While ripping one of my cds on my laptop this happened: Message from syslogd@theirongiant at Thu Jul 5 09:52:16 2001 ... theirongiant kernel: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0" from the kern.log: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0"

Hi folks, I meant to send this in to the devel list a while ago (1 Jul, actually) but school has until recently had a strangehold on me. The issue is this: the sshd.pam.generic in the openssh-2.1.1p4/contrib directory can be modified to suit standard SuSE 6.4 configurations as thus: {crimsun@[dhcp1520]:~} diff -c /etc/pam.d/sshd openssh-2.1.1p4/contrib/sshd.pam.generic *** /etc/pam.d/sshd

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

Dear Colleagues: Through your help an R related installation issue was resolved, but I now have the following usage issue. On any "get.var.ncdf" usage I am seeing: Error: in routine alloca() there is a stack overflow: thread 0, max 535822282KB, used 0KB, request 24B The same error is posted on a file as small as 50MB and as large as 500GB, with ulimit set to unlimited. I

Hi, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k