similar to: congratulations :)

Hi, I have a question on fsync() and ext3's journaling modes. Assume that I call fsync(fd) on a file. If that file is in 'data=journal' mode, would the fsync() return once the data gets safely into the journal ? On the other hand, if that file is in 'data=writeback' mode, would the fsync() return only when the data gets safely into its actual location ? Any help is

Hi, ext3-0.9.18 is now available for 2.4.19-pre8. Some of the fixes in this release are already in the 2.4.19-pre8, but there are some important new fixes in the patch and users are encouraged to upgrade. This release fixes all known outstanding bug reports. The full patch against linux-2.4.19-pre8, and a tarball of the individual fixes in this patch set, is now propagating to

Hello! I got oops after about 3 hours of uptime. Load was about 1,5. This is output of ksymoops after forced reboot if it helps someone. :-) ksymoops 2.4.0 on i686 2.4.14-pre8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.14-pre8/ (default) -m /boot/System.map-2.4.14-pre8 (default) Warning (compare_maps): mismatch on

On Sun, 11 Apr 2010 18:03:00 +0300, Avi Kivity <avi@redhat.com> wrote: > On 04/09/2010 05:56 PM, Ben Gamari wrote: > > On Mon, 29 Mar 2010 00:08:58 +0200, Andi Kleen<andi@firstfloor.org> wrote: > > > >> Ben Gamari<bgamari.foss@gmail.com> writes: > >> ext4/XFS/JFS/btrfs should be better in this regard > >> > >> >

hi, - big and ugly mail. If you don't like them, delete it now :-) - I have collected and classified some information of: http://home.earthlink.net/~rwhron/kernel/bigbox.html And I observed that ext3 performance is worse than previous kernels(2.4.19...). -ac and -aa are here only as reference. Complete information is in the upper URL. dbench: Performance is worse. dbench (Numbers are in

Hi All, A colleague of mine is using syslinux-3.20-pre8, syslinux.com, under DOS to install syslinux loader. It gives "sector read error". He re-compiled syslinux.com under a linux box, and used it successfully to install the loader from DOS. He is installing it on a hard drive (C:) He booted from a floppy and ran: "syslinux.com C:" at A:\ prompt He tried with

Hello, We found that fsync and fdatasync syscalls sometimes don't sync data in an ext3 file system under the following conditions. 1. Kernel version is 2.6.6 or later (including 2.6.8.1 and 2.6.9-rc2). 2. Ext3's journalling mode is "data=journal". 3. Create a file (whose size is 1Mbytes) and execute umount/mount. 4. lseek to a random position within the file, write 8192 bytes

I don't think that XFS is a desktop filesystem at all. This is from XFS FAQ: qoute ------------ Q: Why do I see binary NULLS in some files after recovery when I unplugged the power? If it hurts don't do that! * NOTE: XFS 1.1 and kernels => 2.4.18 has the asynchronous delete path which means that you will see a lot less of these problems. If you still have not updated to the 1.1

> > To be clear, I am not saying there is no bug - there might be. > I performed the following test with several versions of Syslinux: 1_ Execute: 'extlinux --once=non_default_label --install /mnt/sda1' ; 2_ In first reboot, the "non_default_label" should be executed; 3_ In second reboot, the default label should be executed. Results: _ 4.05 to 4.07: OK. _

hi Peter, everyone, I recently installed extlinux on my CF drive. after a few botches, it works, with menu.c32 too. Heres a few notes/observations: - menuing seems pretty sensitive to presence of tabs in extlinux.conf, unlike with pxelinux.cfg/default, Is this an oversight, or something Im misremembering ? - extlinux doesnt have the timeout after menu-choice. if I dont choose, it times out and

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

Hi, can someone tell me whether applications can expect the write requests they make to be executed in order? For instance, suppose an application requests that a file be deleted, and then that another file be moved to an unrelated place. Will these events always happen in that order? Or to put it another way, if something unexpected happens in the meantime (say the computer crashes), is it

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

I have just pushed out SYSLINUX 3.70-pre8. The two main differences is that I have updated the gPXE source base, and added a sanboot module (sanboot.c32). sanboot.c32 *should* be capable of initiating an iSCSI or AoE boot, but I haven't actually tested it. The other main difference is that gPXE now advertises HTTP/1.0 instead of HTTP/1.1, since the code was not actually HTTP/1.1

From: Tim Deegan <Tim.Deegan at cl.cam.ac.uk> Fix register constraints of final jump to kernel entry. When compiled with some GCC versions, mboot.c32 would clobber the kernel load address and try to jump to 0x2badb002. Signed-off-by: Tim Deegan <Tim.Deegan at cl.cam.ac.uk> --- --- syslinux-3.20-pre8/com32/modules/mboot.c.orig 2006-05-22 11:06:17.000000000 +0100 +++

Hi, well, I was finally able to build syslinux-5.11-pre8 from git, but the system doesn't boot with the self-compiled version. All I see is: http://666kb.com/i/cfplluqpcy6owptq3.jpg Build log can be found in http://www.syslinux.org/archives/2013-July/020452.html After I installed the self-compiled syslinux version, I run this commands: # cd /boot/extlinux # rm -rf *.c32 # extlinux

Btrfs had some issues with fsync()''ing directories and fsync()''ing after renames. These three new tests cover the 3 different issues we were seeing. This breaks out the dmflakey stuff into a common helper to be shared between generic/311 and generic/321. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- V1->V2: rename test to generic/321 -removed an

I have released SYSLINUX 3.11-pre8; this is a release candidate. The differences versus -pre6 is that I have reverted the PXELINUX stack changes I did in SYSLINUX 3.10 since there are confirmed reports that they break at least one platform. As before, I hope to release 3.11 on Tuesday unless I get objections. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

On Sat, Nov 7, 2015 at 5:03 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > How about 'strace mkfs.ext2 ..' and see if any system calls are > returning errors. That would show you whether nbd-client is throwing > errors away, or whether mkfs is getting the errors and ignoring them > (seems pretty unlikely, but you never know). > > After that, it'd be down

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken