similar to: oops 2.2.19 ext3 0.0.6b prune_dcache

Hi, i think this message should be removed ;) paradigm:~# umount /mnt2 paradigm:~# mkdosfs /dev/fd0 mkdosfs 2.5 (07 Jan 2000) paradigm:~# /tmp/syslinux /dev/fd0 paradigm:~# sync paradigm:~# mount /dev/fd0 /mnt2 VFS: Can't find an ext3 filesystem on dev fd(2,0). Flo -- Florian Lohoff flo@rfc822.org +49-5201-669912 Why is it called "common sense"

Hi, i am running basically this from cron: /usr/bin/doveadm -v expunge -u * mailbox INBOX.Spam SENTBEFORE 90d /usr/bin/doveadm -v expunge -u * mailbox INBOX.Trash SENTBEFORE 90d /usr/bin/doveadm -v expunge -u * mailbox INBOX.Junk SENTBEFORE 90d Now i am experiencing that the first line e.g. expunging INBOX.Spam returns the error code 68. No syslog/Output whatsoever. I tried running with -vvv -D

Hi Aki, On Wed, Sep 06, 2017 at 11:26:30AM +0300, Aki Tuomi wrote: > On 05.09.2017 14:39, Florian Lohoff wrote: > > Hi, > > i am running basically this from cron: > > > > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Spam SENTBEFORE 90d > > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Trash SENTBEFORE 90d > > /usr/bin/doveadm -v expunge -u * mailbox

Hi, i am transitioning from a samba3 to a samba4 installation and while at it i noticed that on samba4 every file access querys the LDAP (openldap) backend for uid/gid names. With samba3 on Debian/Squeeze i dont see this happening. My assumption was that nscd would cache away those querys which it doesnt on the samba4 wheeze installation. [2015/01/09 15:21:46.331508, 3]

Hi! Short time ago our Samba-Server crashed during normal use with low load. (Ping was working, but no login was possible (didn't ask for password on the terminal)). Perhaps it is a bug, or perhaps it is a problem with my machine and you can help me. I am running: SuSE Linux 6.4 Samba Version 2.0.6 (smbd) Kernel: 2.2.14 (original SuSE-Kernel) Some Logfiles: /var/log/warn ... Aug 16

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

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:

Hi, just had an oops while spool uucp mails via uuxqt->postfix->procmail to multiple mailboxes on an UDMA IDE drive on my Laptop. All filesystems are ext3 and i am running 2.2.19 + ext3 + ide udma patches. When rebooting the system hang - After another reboot everything went smooth. invalid operand: 0000 CPU: 0 EIP: 0010:[<c014ca15>] Using defaults from ksymoops -t elf32-i386

Hi, oops in iput - Kernel 2.2.19/i386 + ide-udma patches + ext3 patches (0.0.7a) Intel BX chipset, SCSI Disks Symbios chipset - The crashing process is the master process of "postfix" an MTA. Just before the crash all processes on that machine started to segfault in nameserver resolution (remote dns server) and after 2-3 minutes this oops happened. ksymoops 2.3.4 on i686 2.2.19.

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

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

An ext3 update which also applies to linux-2.4.16 is available at http://www.zip.com.au/~akpm/linux/ext3/ Quite a lot of miscellany here. It would be appreciated if interested parties could please test it in preparation for sending upstream. Thanks. Changelog: - Merged several ext2 sync-up patches from Christoph Hellwig - Drop the big kernel lock across the call to block_prepare_write.

Conclusion: DO NOT USE SOFTWARE RAID-1 WITH EXT3 I've started with this conclusion cause i am positive that raid-1 and ext3 are causing data corruption. I've upgraded from 7.1 to 7.2 and from the first date i run into data corruption problems @ least once per day (i was monitoring once per day only) after 7 days we bought a brand new server cause the previous was very old and i thought

The system stopped responding to ssh but still responded to ping. The logs showed this error: (its long) Feb 4 00:08:08 server1 kernel: gdmgreeter: page allocation failure. order:0, mode:0x50 Feb 4 00:08:08 server1 kernel: [<c014f863>] __alloc_pages+0x28b/0x29d Feb 4 00:08:08 server1 kernel: [<c014b70f>] find_or_create_page+0x39/0x72 Feb 4 00:08:08 server1 kernel:

Hey all, Long time user of Centos, I really love what you guys are doing here. I have a farm of 50 Centos 4.1 machines. (originally 4.0 updated with yum up to current 4.1). Ever since I updated to the 2.6.9-11 kernel I am getting a lot of kernel panics. 7 machines suffered kernel panics over the weekend. Funny that they were the only ones that are booted into the new kernel! The rest

Hi posted this on the forum but then found the mailing list :-) so hope it's ok to post to the list aswell. we have a centos 4.3 server running samba, winbind and squid authenticating by winbind to our NT domain. Once in a while in the early hours it has the below error in /var/log/messages this causes the machine to fail and we carn't connect to it. It's double dutch to me,

On 05.09.2017 14:39, Florian Lohoff wrote: > Hi, > i am running basically this from cron: > > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Spam SENTBEFORE 90d > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Trash SENTBEFORE 90d > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Junk SENTBEFORE 90d > > Now i am experiencing that the first line e.g. expunging INBOX.Spam >

Hi, from time to time i am having mails delivered to my anon maildrop which completely break mailbox listing. I ignored it mostly as this is an anon maildrop for one time emails so loosing spam wasnt an issue. Today i had a mailbox which wouldnt list at all which was caused by 50 consecutive mails beeing broken. (I am showing the last 20 in the web interface) After some debugging i found a bunch

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

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.