similar to: Is there a 0.0.7a patch for redhat 2.2.19 errata?

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, 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.

Hello All, I have a production server that is running 2.2.20. This server *has* to be up 24X7 - what I'm wondering is: 1) Is ext3 on 2.2.20 rock stable? Or, would you recommend that I just stay with ext2? 2) I have looked far and wide for a the ext3 patch for 2.2.20 - where can I find it? 3) Were are the e2fsprogs that are appropriate to run with the 2.2.X kernel series? Thanks,

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).

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 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

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

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"

I downloaded nilo and oskit from www.nilo.org. Added pcnet32.c linux-2.0.39 driver to oskit. Compiled nilo with pcnet32 and produced boot floppy image. Use it inside vmware vm. My aim is to be able to test pxelinux using vmware+nilo and not a real machine. Floppy starts, detects nic, receives ip from dhcp server, requests boot image to tftpd-hpa, then crashes when talking to tftp. Is

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

SAMBA_2_0 as of 1 mar 2000, 11:00 GMT rh61 kernel-2.2.14. 1) smbpasswd the -x switch was added but now: a) you can't do "smbpasswd -an user" anymore, it asks for password. b) smbpasswd -n user -> seg fault 2) ./configure --with-utmp: make all ... Compiling smbd/connection.c smbd/connection.c: In function `utmp_update': smbd/connection.c:349: structure has no member named

linux 2.2.19/rh6x I use in a share veto files = /.*/ whenever you connect to it the client process hangs, the smbd starts consuming cpu time and cannot be killed but with "kill -9". This is the last part of the smbd log [2002/05/16 05:49:51, 3] smbd/sec_ctx.c:set_sec_ctx(319) 3 user groups: 100 6 19 [2002/05/16 05:49:51, 3] smbd/trans2.c:call_trans2findfirst(863)

Hello, Now that kernel 2.2.20 is out with security fixes, I'd be interested in using it with ext3. The latest patch for 2.2.19, 0.0.7a, applies with some offset (both with and without kdb), and even compiles (without kdb), but I scarcely know what I am doing so haven't tried it yet. Could people in the know enlighten me on that point? I guess there is little chance for another ext3

I've not been happy with the stories about the "stable" 2.4.x kernels. Everywhere I read people saying "not for production use". Would you recommend adding ext3 to 2.2.19 (ext3-0.0.7a) or moving to 2.4.1x and using ext3 there (ext3-0.9.12)? -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen@ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

Hello, I'm usign Kernel 2.2.19 with ext3 0.0.7b patches. I'm also using cbq to control bandwidth. The cbq is correctly creating the classes and queueing disciplines but, whenever I call cbq stop I get a kernel panic: > Aiee, killing interrupt handler > Kernel panic: Attempted to kill idle task! > In interrupt handler - not syncing The exact line in cbq script that is

3.0.25rc1 has the same issue. On Fri, 06 Apr 2007 22:52:05 +0200, Giulio <giulioo@gmail.com> wrote: >Vista32 >3.0.25pre2 (I understand vista patches for "share level" are already in) >security = share (with "valid users" on share definition) >host msdfs = no > >user/pass in smbpasswd file. > > >If I use "connect network

This is the list of problems I had with samba-2.0.6 so far. Can anyone tell me if he can reproduce them and if he considers them as problems? 2.0.6 on linux 2.2.13 or 2.0.33 1) sighup/log reopening doesn't always work: connections that are already active keep logging to the old logs; logrotate rotates/zip the logs and samba stops logging completely till restart. 2) Localized chars. I have

The 2.04b rpm for rh60 ships with and installs a config file for logrotate (the samba.log file in the packaging/RedHat section). ===== /var/log/samba/log.nmb { postrotate /usr/bin/killall -HUP nmbd endrotate } /var/log/samba/log.smb { postrotate /usr/bin/killall -HUP smbd endrotate } ===== 1) I think that the use of "endrotate" is wrong. There is no