similar to: obsolete update blush call.

Hello everyone, I've just lost my whole EXT3 linux partition by what was probably a bug. For your reading pleasure, and in the hope there is enough information to fix this problem in the future, here the story of a violent ending: This tragic history starts actually on windows: MS Word had wiped out an important file on a floppy, and I got the task of retrieving what was possible. Using

A mysql database file was copied over to a new box running Fedora Core 1. The kernel was updated to the latest Fedora release. However mysqld complains about corrupted tables. The kernel was then updated to 2.6.5 mysqld still complains about corrupted tables. Hardware: Dual PIII 800. 3ware RAID dmesg: ... ... ... EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in

I recently ran into an issue where I couldn't create a file larger than 2GB on a particular ext3 filesystem. I was under the (mistaken) impression that >2GB support went in before ext3 support, and all ext3 filesystems would therefore support >2GB files on ia32. So, I started poking around and found that some of my ext3 filesystems have the "large_file" feature flag set on

Get this warning on bootup ext3 file checks on 2.6.* kernels. Apparently harmless, but how do I fix this? _______________________________________________ debian-knoppix mailing list debian-knoppix at linuxtag.org http://mailman.linuxtag.org/mailman/listinfo/debian-knoppix

----- Message d'origine ---- > De : David Baron <d_baron at 012.net.il> > ? : wine-users at winehq.org > Envoy? le : Jeudi, 28 F?vrier 2008, 18h53mn 08s > Objet : Re: [Wine] How about this replacement of WINE. > > > However, it's a great, great project IMO. It was about time something > > > like that should've been made. Redirecting calls is simply

Hi everybody, I had a problem which you may be interested in. I set data=writeback in /etc/fstab for each of my ext3 partitions (because it complains on "mount -o remount,data=writeback" with "ext3: journal mode can't be altered on remount" or similar) and rebooted. Problem: / was mounted read-only, I couldn't remount it (because mount appends the options from fstab,

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

wine: Unhandled page fault on read access to 0x409ffd80 at address 0x4000ba7c (thread 0009), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 32") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger This happens on everything I try run. Note: Still a problem with latest upgrade. It may have more sideeffects than

This is probably an idiot (and certainly so basic as to be non-Dovecot) question, but I have been chasing my tail for a day or so on it, so I will, with humiliation, ask for guidance on it. Some time back I had asked if dovecot had to have a whole build tree of stuff to run or if any upgrade could be limited to just the executable and some libraries. I was told the latter, and given this

What is the correct procedure to fsck a ext3 partition? A system died during a 7.2 upgrade - /usr and /home were selected to convert to ext3 - and I did a fsck -t ext2 /device but the system still complains that the file system is/was not clean unmounted. TIA

Commit-ID: 52251e210c7a21068063fe16a3874903d3f1aa14 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=52251e210c7a21068063fe16a3874903d3f1aa14 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 20:39:46 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 8 Oct 2019 00:13:20 +0100 [klibc] fstype: Drop obsolete

Hi, Just got Fedora FC1 vanilla 2.4.25kernel+libata8patch booting problems, FC1 complains that it can not automatically find&found partitions specified with "LABEL=" in /etc/fstab, and then falls me into repair mode. In the repair mode I can mount it manually without any problems. More interesting are: 1) I have several partitions specified with "LABEL=*" in

Hi folks, Is it possible to resize an ext3 filesystem while it's online? It looks like resize2fs won't do the trick unless the filesystem is unmounted. And ext2resize takes one look at the filesystem while it's mounted and complains as well, this time about un-supported features. It's not a huge deal if I have to shutdown the system to grow the two filesystems, it's just

Well I thought someone might be interested in this. I have a Compaq server with a cpq array in a raid 5 configuration with some bog standard video card no sound card, NO X installed, no applications/modules not included with the distro, and 256 megs of memory. I upgraded it (yes I know not supported but...) from Roswell to 7.2 in the middle of last week and installed all applicable errata

I have a Fedora Core 3 system at home, that was running fine, but now won't boot. Someone shut the power off on it without doing an orderly shutdown, and also I sometimes apply patches with "yum -y update" without doing a reboot immediately afterward - I suppose either of these could be related to my system not booting. I have a lot of information about the early stages of the

Hey there, I downloaded the Kernel Source 2.2.17 from the ext3 site, however I can't seem to figure out how these rpm's work (I don't like RPM's and I rather not use em either :-( no offense :-)) and I kinda miss the good old simple .tgz files which show me where they extract and I can compile myself n stuff. Anyways I tried rpm -iv <package name> then some stuff happened

In August I reported a problem with the sys_ftruncate call that caused me to reboot my machine. I didn't see any responses to it then on the ext3 list, and the problem is now recurring, so I thought I'd try again. I don't think I've rebooted since the last problem. In the last few days it hasn't taken as long as 17 hours, but it has sometimes taken unusual and uncomfortable

Several times recently my "mutt" email program has looped for hours at a time in the middle of a sys_ftruncate call. This happens when I use the "$" command to write changes out to my mailbox. It does eventually return from the call and everything seems to have worked ok. But in the meantime the CPU is pegged, $MAIL is locked so I can't receive new mail, and signals to

udevadm is included in all reasonable recent distributions. This avoids 'command not found' errors in verbose mode. Signed-off-by: Olaf Hering <olaf at aepfle.de> diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index e6d5fde..0db56e4 100644 --- a/daemon/guestfsd.c +++ b/daemon/guestfsd.c @@ -54,7 +54,6 @@ #include "daemon.h" GUESTFSD_EXT_CMD(str_udevadm, udevadm);

I have a Debian system from a Knoppix distribution. I started out with ext2 but decided to change to ext3. tune2fs -j OK. However the system boots with a warning ....ext3 mounted as ext2. proc/mounts confirms this and no journal is running. So I have to make an initrd. Did so using instructions in the Debian Reference and this did not change anything. Any attempt to use the img produced was a