similar to: ext3 htree issues

I thought I've found three bugs on syslinux 6.03: (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and MENU COLOR UNSEL but uncommented MENU COLOR SEL: A black "border" is displayed below the selected line and on its right edge. (2) Uncommenting MENU COLOR UNSEL: This effect appears also on separators and on right edge on every unselected lines. (3)

hi, I want to make some changes in ext3_unlink code to make undelete works, i read a lot about it and im planning to put this lines in that function: if (IS_UNDEL(inode)){ trash = ???? ext3_link(dir,dentry,trash); //make a hard link } somebody know how do i get a especific directory dentry using the ext3 functions ? (im planning to use the inode 6 or inode 11 that somebody said that usually

Hi, I'm having a problem with ext3 on my system. I'm running 2.4.13 with the appropiate ext3 patch and a software raid array with paritiions as shown below: Filesystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611:

I realize this might be one of those religious topics, but is there any good rule of thumb as to how to setup storage for a Xen domU? Without really knowing any better, I''m basically going to make a disk image of the OS and the create a ''data'' partition on my raid 5 volume for each virtual machine. This is for use at home, so in reality it probably doesn''t

On Wed, Dec 9, 2015 at 1:07 PM, Emilio Lazo Zaia via Syslinux <syslinux at zytor.com> wrote: > I thought I've found three bugs on syslinux 6.03: Just to be clear, is this only affecting vesamenu.c32? > (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and > MENU COLOR UNSEL but uncommented MENU COLOR SEL: > > A black "border" is displayed

Hi I have mailed about this previously, but back then it was not really confirmed, so I have let it be at that. Anyhow, problem is that for some reason 2.5/2.6 ext3 with HTREE support do not like what perl-5.8.0 does during installation. It *seems* like one of the temporary files created during manpage installation do not get unlinked properly, or gets into the hash (this possible?) and cause

Hi All, I just had "an issue" with my Linux 2.6.1 kernel. While working, I tried to rf -rf a directory, and was told my filesystem was mounted readonly (which it wasn't). I then shut the machine down, and on shutdown, I got a "kernel BUG at fs/ext3/super.c: 411". Full report below: Mike [1.] One line summary of the problem: Filesystem became readonly, then

Over the last two days we've been seeing a fair bit of this: ---- # ls -laR > /dev/null ... ls: ./server2/b/user/bxyz/392.: Input/output error ---- This is with the latest htree patches applied to 2.4.19, and latest e2fsprogs-test, on a dual AMD system, with 5x73GB SCSI drives on a MegaRAID controller. We're using the gcc 2.96 that comes with RH7.3. esfsck shows "Inodes that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, today i re-organized my data, lots of "mv" and "cp". then, upon unmounting a ext3 partition the following was shown on the console: (the leading "Mar 22 02:40:04 sheep kernel:" is cut here) - ------------------------------- ~ sb orphan head is 940994 ~ sb_info orphan list: ~ inode sdd4:940994 at cf852874: mode

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In additin to the 'brelse' issue I mentioned a few days back, I'm seeing new messages in my logs about ext3 trying to unlink non-existant files. any ideas? log mesages are below: Oct 5 19:34:40 linux-sxs kernel: EXT3-fs warning (device sd(8,19)): ext3_unlink: Deleting nonexistent file (1433981), 0 Oct 5 19:38:32 linux-sxs kernel: VFS:

Hi, I'm having a problem with ext3 on my system. I'm running 2.4.13 with the appropiate ext3 patch and a software raid array with paritiions as shown below: Filesystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G

Hello Andrew, I patched 2.4.20 with your patch found out on http://lwn.net/Articles/17447/ and I have a big problem with: once server is booted on 2.4.20 with your patch, when I want to reboot with /sbin/reboot, server makes a Segmentation fault and it crashs. I tested it on 50-60 servers and it is the same problem. I tested kernel 2.4.20 without your patch: no problem. # uname -a Linux XXXXXX

Hi all. I have one server with problem in maillog: Feb 6 06:46:26 host1 postfix/qmgr[24296]: fatal: qmgr_move: update active/4DE015AC536 time stamps: Stale NFS file handle Feb 6 06:46:27 host1 postfix/master[4487]: warning: process /usr/libexec/postfix/qmgr pid 24296 exit status 1 Feb 6 06:46:27 host1 postfix/master[4487]: warning: /usr/libexec/postfix/qmgr: bad command startup -- throttling

Help! I am running FC1, with a maxtor 160GB HD installed. Drive is only about a month old. I had just finished moving data from an older HD that was making some funny sounds and throwing some random errors. All was well. Last night we lost power for several hours and 1 machine's UPS/shutdown system didn't power down the workstation. The other 7 in our office did fine. The power

I wanted to boot gentoo on xen, but it doesn''t work. What can I do? Booting ''Xen 3.0.0 / Linux 2.6.12.5'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=131072 com1=115200,8n1 [Multiboot-elf, <0x100000:0x641cc:0x27e34>, shtab=0x18c078, entry=0x100000] module /vmlinuz-2.6.12.5-xen-0 root=/dev/md0