similar to: ext3 dead after testing 2.6.0-test5

There's a new set of ext2/3 patches for 2.4.21-pre5 available at: http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21pre5-2 and in broken out form at: http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21pre5-2 New to this patch set include: * A kludge to help htree work well with Linux's NFS implementation * Allow the orlov allocator to be disabled via a

Hi all! I have a slight problem: I have an external disk which contains one big filesystem (like a floppy) type ext3 (If you ask why: blame udev or maxtor, or me because I am stupid) which is approx 60% filled. Now I want to have a partition table, ie a layout where the current filesystem is the first partition, and the rest is as usual. Is this possible withotu destroying the data? Best

Hi rsync gurus! [Please Cc: me, as I am NOT subscribed to the list!] First the data points: debian/woody, local server=i386 arch, remote is alpha arch rsync version on both debian 2.5.5-0.2 While upgrading our server to a raid we were hit by a bug which I really consider very strange: The option -n/--dry-run does NOT change files, but DELETE files when called with --delete. Test case I had: $

Hi all! Several times now I have seen the following: fsck-ing the ext3 fs I get hundreds (if not thousands) of messages: Indoe NNNN, i_blocks is K, should be (K-8). FIXED: Interestingly the difference is *always* *always* *always* 8. Can someone explain me what was going on? Why this? Thanks a lot and all the best Norbert

Hiall! Is there un updated patch for bridge/nf/ebtables for 2.4.27? I tried the patch for 2.4.26 but there were several rejects. Then I patched in the rejects by hand and it zorked, at leqst for now. But to be sure I want someone with knowledge to update the patch instead of me nokey ;-) Best wishes Norbert -------------------------------------------------------------------------------

An update to the ext3 filesystem for 2.4 kernels is available at http://www.uow.edu.au/~andrewm/linux/ext3/ The diffs are against linux-2.4.7 and linux-2.4.6-ac5. The changelog is there. One rarely-occurring but oopsable bug was fixed and several quite significant performance enhancements have been made. These are in addition to the performance fixes which went into 0.9.3. Ted has put out a

HI list! We regularly experience kernel Ooops on our alpha SX164 with ext3 on md on ide controller: No modules loaded, lsmod empty, self compiled kernel ksymoops 2.4.5 on alpha 2.4.25. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.25/ (default) -m /boot/System.map-2.4.25 (default) Warning: You did not tell me where

Dear all, (please Cc) yesterday I had two bugs with btrfs and ext3 occurrences, always happening when plugging in an external USB btrfs disk. Today I had a BUG which is purely ext3 related. The last bug was with yesterdays latest git checkout. Here are the three bugs/oops: that one was with 3.0.0-rc2 (exactely) Jun 10 14:50:23 mithrandir kernel: [40871.704129] BUG: unable to handle kernel

Hi Alan, thanks for your answer. > I do not recognize this problem based on your description. Please post > the dmesg log. Here cleaned output of journalctl, removed mainly networkmanager stuff. This is about a wake up after sleep, where before the stick was ok. More details necessary, let me know. Thanks Norbert

Hi Alan, sorry for the journalctl output. I have now done the following:L * boot into 3.17-rc7 * mount the usb stick (recovery completed) * unmount, mount, unmount - just to be sure all is fine * started usbmon capturing on bus 3 * mount the usb stick * suspend to ram * wake up now the stick is "officially" mounted (/proc/mounts) * umount error messages pop up * try to mount more

On Sun, 28 Sep 2014, Norbert Preining wrote: > Hi Alan, > > thanks for your answer. > > > I do not recognize this problem based on your description. Please post > > the dmesg log. > > Here cleaned output of journalctl, removed mainly networkmanager stuff. I would have preferred to see the output from dmesg, as I requested. But never mind, there probably

- Fixed startup crashing in POP3 server - Several fixes to opening index file which needs to be rebuilt. Before it didn't always rebuild the index but just fallbacked to using only memory, and that could have been quite slow since all mails in the mailbox were opened and parsed. - If there's nothing in mail_cache_fields, index rebuilding doesn't open the file anymore. This should

Again at http://dovecot.procontrol.fi/test/ if someone wants to test it. - new index file code should work now - mbox support is completely broken - caching isn't very smart yet. it always caches only what client requested at the time - header caching might have some problems actually now that I think of it.. I was anyway going to change a bit how it worked.

Dear all, (please Cc) I am running latest kernel (3.17-rc6) and I see corruption of an usb3.0 device usb stick. Strange errors, impossibility to mount. Repeated unplugging and replugging helps sometimes, in all cases recovery is necessary. Is this a know problem, a problem of my system Debian/sid, uptodate, self-compiled kernel of the suspend program (that initiates the suspend), the usb

On Mon, 29 Sep 2014, Norbert Preining wrote: > Hi Alan, > > sorry for the journalctl output. I have now done the following:L > > * boot into 3.17-rc7 > * mount the usb stick (recovery completed) > * unmount, mount, unmount - just to be sure all is fine > * started usbmon capturing on bus 3 > * mount the usb stick > * suspend to ram > * wake up > now the

On Sat, 27 Sep 2014, Norbert Preining wrote: > Dear all, > > (please Cc) > > I am running latest kernel (3.17-rc6) and I see corruption of an usb3.0 > device usb stick. Strange errors, impossibility to mount. > > Repeated unplugging and replugging helps sometimes, in all cases > recovery is necessary. > > Is this a know problem, a problem of my system >

Hello-- We have a system where a central server formats removable hard disks, which are then booted in an embedded system running a highly modified RH9. The removable disks themselves contain boot, root, and data filesystems. The problem we've encountered after upgrading to FC3 / kernel 2.6 on the central server is that the 2.4 kernel in the embedded system cannot read the root filesystem,

I just followed the railscast http://asciicasts.com/episodes/266-http-streaming to have streaming. calling the http://localhost:3000/users ends up with following error: [INFO] NameError (uninitialized constant ActionView::StreamingTemplateRenderer::Fiber): [INFO] /home/kristian/projects/sandbox/rails3.1/rails3.1-test5/ target/rubygems/gems/actionpack-3.1.0.rc4/lib/action_view/renderer/

Hello everybody. I have a strange problem with cifs and Samba share. I have a Qnap NAS server (TS-109) and I would like to have a private share where I could keep my stuff and access them through Windows and Linux. But I have an odd problem and I can't tell what's wrong. I can write new files on a share, I can update them but I can't write on special occasions. And because of this

Hello, there are problems with quota dict when multiple dovecot deliver processes are launched in parallel. It can be reproduced by sending a mail with multiple different recipients - the mail is delivered OK to all recipients, but the quota are not updated correctly in sql. I looked at the code and it seems that the problem is somewhere in dict cache. If I configure in Postfix max number of