similar to: linux-2.2.19pre14.ext3.diff

Hi, ext3-0.0.6a has been uploaded to ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ext3-0.0.6a.tar.gz and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ext3-0.0.6a.tar.gz This version changes the way dirty buffers are marked to protect against device drivers which might block in the ll_rw_block() function. (Loop and lvm are examples.) It should also fix a rare but persistent report of

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops

Christian Lademann wrote: Hi. Is there any reasonable possibility to check a mounted fs for errors? It would be useful to have server-filesystems (and harddisks) checked periodically on machines that are only rebooted by hardware-failures ;-) Regards, Christian -- * Christian A. Lademann, ZLS Software GmbH mailto:lademann@zls.de * ZLS Software GmbH * Frankfurter Strasse 59

Hi. What is the state of ext2resize for Ext3? How about the online-ext3-patch? Regards, Christian -- * Christian A. Lademann, ZLS Software GmbH mailto:lademann@zls.de * ZLS Software GmbH * Frankfurter Strasse 59 Postfach 1628 mailto:zls@zls.de * D-65779 Kelkheim D-65766 Kelkheim http://www.zls.de * Telefon +49-6195-9902-0 Telefax

Hi. Is there any reasonable possibility to check a mounted fs for errors? It would be useful to have server-filesystems (and harddisks) checked periodically on machines that are only rebooted by hardware-failures ;-) Regards, Christian -- * Christian A. Lademann, ZLS Software GmbH mailto:lademann@zls.de * ZLS Software GmbH * Frankfurter Strasse 59 Postfach 1628

I previously wrote: > OK, my previous patch cleans up the ASSERT for invalidate_buffers() > (modulo the fact that it was missing a ')' at the end of the line) > but it hasn't really fixed the whole problem. If a file write is in > progress when invalidate_buffers() is called, I get an oops: > The oops is caused from __invalidate_buffers() calling put_last_free(bh) >

Well.... you might remember that I have had problems will my NFS fileserver that run ext3 with data=journal. The filesystem corruption now seems too be solved with the patch (plus amendment) that I posted, so I am happy about that... but there is more. I have known for a while that ext3 doesn't behave very well when the journal fills up. If it finds that the journal is full, and the

Hi, * gurus, I wonder if there is a way to alert the in-house extension(s) in case of an incoming external call without actually answering it, before somebody picks up the phone on one of the extensions? This way the caller wouldn't have to pay for the call until somebody answers. Regards, Christian Lademann

** ** I posted this message quite a time ago. Some people use my patch and I ** receive queries for a recent version from time to time. This patch didn't ** make it into the mainstream distribution yet. Sorry. ** ** This is the updated version for Samba-1.9.17p1. ** Hello, people. I have implemented some enhancements for Samba: 1. dynamic configuration-values 2. configurable

Our main NFS-server, running Debian Potato, died this morning whilst under quite heavy load - due to a runaway perl-script forking of some 200 instances of "/bin/cp" (the load was ~ 50). The server is running 2.2.19pre14 with ext3-0.0.6b. The server is running kernel-nfs. Assertion failure in journal_dirty_metadata() at transaction.c line 796: "bh->b_next_transaction ==

Hi, I was surprised that apply and sapply don't return the same results in the example below. Can someone tell me what I'm missing? > zls <- function(x) character(0) > m <- matrix(0, nrow=2, ncol=2) > apply(m, 1, zls) character(0) > sapply(m, zls) [[1]] character(0) [[2]] character(0) [[3]] character(0) [[4]] character(0) > R.version _

after install libguestfs_xfs, all results are: [using guestfish] guestfish -N fs:xfs -m /dev/sda1 statvfs / bsize: 4096 frsize: 4096 blocks: 24713 bfree: 23391 bavail: 23391 files: 51136 ffree: 51133 favail: 51133 fsid: 2049 flag: 4096 namemax: 255 [using virt-rescure] virt-rescue -a test1.img ><rescue> mount /dev/sda1 /sysroot ><rescue> stat -f /sysroot File:

Hello, http://dev.rubyonrails.org/wiki suggests to: Create a patch with your changes: svn diff > my_properly_named_patch.diff but how this proper name looks like? olegf

Here's one last plea for help from the list before I give up on the totally cool software FAX modem concept in complete despair (for now, at least, until I have more time to dig into it).... I am simply not able to successfully receive a FAX no matter what device I transmit from or how I bring the call into Asterisk. My lastest effort was a call from a Pitney-Bowes FAX machine into an X100P

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Is there a way to force dovecot to reprocess a user account to refile the m.* files based on new config for max file size. Ive got one account at 22k files due to a 2M split.