similar to: EXT3 with 2.2.20 - Is it stable enough for a production server th at is used 24X7?

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

Hi, I installed a 2.4.18 kernel, with ext3 support and make a tune2fs -j /dev/sdxxx with all partitions, now I want to run a 2.2.20 kernel, I want to know if I can use the patch for 2.2.20 series (0.0.7a) without problems with my new ext3 partitions, or I must mount it as ext2 from 2.2.20, greetings and reply to admin@cideweb.com, I'm not subscribed to the list.

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.

Hey everyone, I am planning to set up a debian server using the 2.2 kernel tree (kernel 2.2.20) I have tried applying the 2.2.19 patch once but it spewed out some rejects. I went ahead and selected yes to the second fs development code. When I converted all my partitions to 'ext3' (by adding a journal) everything seemed to go well, but when I rebooted (bad shutdown) the computer during

Hi, since my last update from the Dovecot Prebuilt Binary for Debian I get a lot of messages like this in mail.log: dovecot: imap-login: Error: SSL: Stacked error: error:0608308E:digital envelope routines:EVP_PKEY_get1_EC_KEY:expecting a ec key Nevertheless Dovecot seems to work normally. Email client doesn't mention any error. This was my last update: Start-Date: 2015-12-04 14:00:31

One of our servers (false) just oopsed. In the middle of lunch. Any advise? On console: false kernel: Assertion failure in journal_start() at transaction.c line 245: "handle->h_transaction->t_journal == journal" In kernel log (ran it through ksymoops): Nov 13 12:35:37 false kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Nov 13 12:35:37

Hello , I am trying to install an ingress qdisc on a slackware 7 , 2.2.20 box . I have installed iproute2-2.4.7-now-ss010824.tar.gz . I `ve built all the QOS stuff in my kernel . Playing with cbq sfq etc works ok . However when i try to setup ingress i get the infamous RNETLINK message tc qdisc add dev eth0 handle ffff: ingress RTNETLINK answers: No such file or directory Something weird ,

see sabj.

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

I am trying to compile 2.2.20 with both ext3 and reiserfs (to easily migrate from reiserfs to ext3 :-) All patches merge nicly, but compile fails because "buffer_journaled" is defined by both reiserfs and ext3. I looked at the "2.2.14 ext3 + reiserfs incompatibility"-thread on the kernel list and figured out that renaming "buffer_journaled" in fs/buffer.c and

Hi I have Xen running on Fedora as a dom0 with domUs of fedora 4, suse 10.0 and my own home grown file system. It all seems to work fine so far and I am about to start some stability testing I need to do. I am using the current unstable tree based on 2.6.12. One thing I have not figured out is a problem I am having with dhcp. When I set dhcp = "dhcp" in my /etc/xen config files

Hi everybody, i'm having serious problems with the configuration of samba 3.0.10. First my setup : samba-3.0.10 built from source openldap-2.2.20 built from source OS : Suse Linux 7.1 (but updated -> Kernel 2.4.27) My problem : ------------ I'm trying to use smbpasswd like the following : ---snipp--- [PTS2] 486dx66:/usr/local/samba3 # bin/smbpasswd -D 10 tina Netbios name list:-

After upgrading to openssh-3.4p1, password authentication is no longer working on my system. I'm running Linux RedHat 6.2 with: kernel 2.2.20 openssh-3.4p1 openssl-0.9.6 pam-0.72-6 pwdb-0.61-0 I've tried it with and without compression, with and without priv sep, and I always get errors like this: Jun 30 19:07:48 sugarfreejazz sshd[1344]: Failed password for randy from 10.10.10.2 port

My system had the following error sent to syslog: kernel: Assertion failure in ext3_free_blocks() at balloc.c line 358: "bh->b_committed_data != NULL" Immediately before that with the same timestamp was a sendmail entry. The system locked up shortly after that. I never saw an oops. I was tailing /var/log/messages in a terminal. That syslog entry was not saved to disk. I have

Hi there, I was wondering if you could give me some pointers as to how to get rid of the spooge of microsoft from our office, and have samba-2.2.2 assuming file sharing duties (read this as the Boss isn't happy with all the win2K crashes on the NIC's) The machine is a Pent-III 850Mhz w/256MB, dual NIC's, and 2 HD's (IDE) with /dev/hda1 being where the OS is stored, and /dev/hdb1

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/

http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig v2.2.20 probably will be released tomorrow or maybe during weekend. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added

http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig v2.2.20 probably will be released tomorrow or maybe during weekend. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added

Hi there I've just upgraded to openssh-3.2.2p1 from openssh-1.2.3 and am having some difficulties. On one of the platforms I'm using (linux kernel 2.2.19 with glibc 2.1.1) it works fine, but on another (linux kernel 2.2.20 with glibc 2.0.7) I get this in the syslog every time I log in: sshd[12277]: Accepted publickey for root from 212.38.67.158 port 2397 ssh2 PAM_pwdb[12277]: (sshd)