search for: 1mib

...nning of device, even though * there is our 1st superblock at 64k. Some possible reasons: * - the first 64k blank is useful for some boot loader/manager * - the first 1M could be scratched by buggy partitioner or somesuch */ #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) " 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I don't know exactly how Syslinux is handling this, but it should be using the whole available space (1MiB instead). -- Paulo Alcantara, C.E.S.A.R Speaking for myself only.

...option that will do what >> the OP wants. > > > The problem with gparted is that it works only in units of megabytes. > There is no way to move a partition to a particular sector or, for > that matter, do much of anything _exactly_. I'm not sure why granularity finer than 1MiB is necessary. But setting that aside, with a rotational drive with 4KiB sectors, you're better off with 1MiB alignment than not being 4KiB aligned at all. Depending on the drive and workload misalignment can cause a brutally bad performance hit. And if it doesn't then I wouldn't worry a...

...out something like this using sda and sdb. Create /boot as 512 MB XFS raid1 array. Create SWAP as 32 GB SWAP raid1 array. Create / on 3.xxx TB XFS raid1 array. I then get error. "Your BIOS-based system needs a special partition to boot from a GPT disk label. To countinue, please create a 1MiB 'biosboot' type partition." I cannot seem to create the biosboot partition so it is mirrored to both drives for redundancy. Any ideas how to do this? I want everything mirrored to both drives.

...ttps://tails.boum.org/ > [details] https://labs.riseup.net/code/issues/8891#note-9 > > Cheers, > -- > intrigeri Any (common) ISO image size should be a multiple of 2048 bytes, as this is the normal bytes_per_sector value. For isohybrid images, the result should be a multiple of 1MiB (1048576 bytes), which is itself a multiple of 2048 bytes. So, in addition to adding the corresponding MBR and partition table to the original ISO image, the isohybrid tool should also check that the ISO image is a multiple of 1MiB. If it is not, then the isohybrid tool should first add a &quo...

...branch target is out of range, LLVM MC will issue an error message to tell users it could not resolve the fixup record. I have compared the result with the GNU assembler. GNU assembler will convert the branch to inverted one plus jump to make the branch possible. The range of unconditional jump is 1MiB. It looks like ########################## bne a0, a1, FAR_BRANCH … FAR_BRANCH: converted to ########################## beq a0, a1, SKIP_J j FAR_BRANCH SKIP_J: … FAR_BRANCH: I found there is a target hook, relaxInstruction, that tries to achieve the similar goal. However, the target hook only re...

Hi, at [Tails] we're in the process of shipping hybrid ISO images by default again. We're using `isohybrid -h 255 -s 63' to do that (thanks to the advice we got on this mailing-list a few months ago!). And then, we've discovered that sometimes, isohybrid produces ISO images whose size is not a multiple of 2048 bytes. Who cares? ... may you ask. Well, apparently, VirtualBox does:

...MC will issue an error message to tell users it could not > resolve the fixup record. I have compared the result with the GNU > assembler. GNU assembler will convert the branch to inverted one > plus jump to make the branch possible. The range of unconditional > jump is 1MiB. It looks like > > ########################## > bne a0, a1, FAR_BRANCH > … > FAR_BRANCH: > > converted to > > ########################## > beq a0, a1, SKIP_J > j FAR_BRANCH > SKIP_J: > … > FAR_BRANCH: > >...

parted fs resize is deprecated. http://savannah.gnu.org/forum/forum.php?forum_id=6837 parted fs move can only move a partition into free space https://www.gnu.org/software/parted/manual/html_node/move.html The thing to do here is use gparted live or Fedora live media and yum/dnf install gparted. It has a move/resize option that will do what the OP wants. Chris Murphy

...o what >>> the OP wants. >> >> The problem with gparted is that it works only in units of megabytes. >> There is no way to move a partition to a particular sector or, for >> that matter, do much of anything _exactly_. > I'm not sure why granularity finer than 1MiB is necessary. But setting > that aside, with a rotational drive with 4KiB sectors, you're better > off with 1MiB alignment than not being 4KiB aligned at all. Depending > on the drive and workload misalignment can cause a brutally bad > performance hit. And if it doesn't then I...

...array. >> >> Create SWAP as 32 GB SWAP raid1 array. >> >> Create / on 3.xxx TB XFS raid1 array. >> >> I then get error. >> >> "Your BIOS-based system needs a special partition to boot from a GPT >> disk label. To countinue, please create a 1MiB 'biosboot' type >> partition." >> >> I cannot seem to create the biosboot partition so it is mirrored to >> both drives for redundancy. Any ideas how to do this? I want >> everything mirrored to both drives. > > Yeah, you need to create the 1M part...

...re is our 1st superblock at 64k. Some possible reasons: > * - the first 64k blank is useful for some boot loader/manager > * - the first 1M could be scratched by buggy partitioner or somesuch > */ > #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) > " > > 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I > don't know exactly how Syslinux is handling this, but it should be using > the whole available space (1MiB instead). > I have tried to get a formal ruling on the use of this from the btrfs crowd, but haven't go...

...me possible reasons: > > * - the first 64k blank is useful for some boot loader/manager > > * - the first 1M could be scratched by buggy partitioner or somesuch > > */ > > #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) > > " > > > > 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I > > don't know exactly how Syslinux is handling this, but it should be using > > the whole available space (1MiB instead). > > > > I have tried to get a formal ruling on the use of this from the btrfs...

...re is our 1st superblock at 64k. Some possible reasons: > * - the first 64k blank is useful for some boot loader/manager > * - the first 1M could be scratched by buggy partitioner or somesuch > */ > #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) > " > > 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I > don't know exactly how Syslinux is handling this, but it should be using > the whole available space (1MiB instead). > > -- > Paulo Alcantara, C.E.S.A.R > Speaking for myself only. The issue about the 64...

Hello Everyone, I am a newbie. When I try to install GRUB2 on centos 5.2 system, I get following error. centos5: grub-install /dev/sda //sbin/grub-setup: warn: This GPT partition label has no BIOS Boot Partition; embedding won't be possible!. //sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE

Hey folks, I've been getting requests from the users that they want the OCFS2 filesystems aligned to 64k boundaries, however, when I began the project, the dummy of me, created the OCFS2 filesystem on top of the whole disk device (no partition) for example, one of the SAN devices would show up as /dev/dm-10, I created the filesystem using the following command: mkfs.ocfs2 -L SOMELABEL

...the difference, in bytes, between the non-hybrid ISO image and > the isohybrid one? Could you please provide both exact sizes? Our current stable release [1], which wasn't a hybrid ISO, is 951764992 bytes. If I run `isohybrid -h 255 -s 63` it becomes 954132480 bytes which is a multiple of 1MiB (and hence 2048 bytes too). This seems to happen for all of our stable releases I tried, and they're all below 1GiB in size... [1] http://dl.amnesia.boum.org/tails/stable/tails-i386-1.2.3/tails-i386-1.2.3.iso > It is > possible that some "limit" (e.g. around the 1GiB) might b...

Hi list (and happy new year), I'm experiencing some troubles using Samba (4.1.17 debian version) over VPN. Basically we've following setup : PC === LAN ===> VPN (WAN) ==== LAN ===> Samba file Server Copying big (say > 1MiB) files from PC to Samba file server almost always ends up with a NT_STATUS_IO_TIMEOUT error (or "a network error occured" if trying to copy from a Windows box). It seems that Samba cannot cope with the fact that LAN speed is way higher than WAN one (thus filling buffers an not waiting...

...}, + { "-9223372036854775808", -1 }, + { "8E", -1 }, + { "8192P", -1 }, + { "999999999999999999999999", -1 }, /* Strings we may want to support in the future */ { "M", -1 }, - /* { "1MB", -1 }, */ - /* { "1MiB", -1 }, */ + { "1MB", -1 }, + { "1MiB", -1 }, { "1.5M", -1 }, /* Valid strings */ diff --git a/src/utils.c b/src/utils.c index 5663043..a7519ec 100644 --- a/src/utils.c +++ b/src/utils.c @@ -1,5 +1,5 @@ /* nbdkit - * Copyright (C) 2013 Red Hat In...

Hi, Ady wrote: > Let's not forget that the goal usually is to select CHS values so that > the resulting (optical and/or other) media would boot correctly in as > many systems as possible Agreed. But we now have a report about failure of 255x63 on a popular pseudo-hardware, when the ISO is presented as DVD-ROM. (Probably there is no complaint when it gets presented as hard disk.)

I will try to get some spec cpu 2006 rate runs done under -O3 -flto with and without -slp-vectorize-hor and let you know. -Thx -----Original Message----- From: nrotem at apple.com [mailto:nrotem at apple.com] Sent: Tuesday, November 10, 2015 3:33 AM To: Charlie Turner Cc: Das, Dibyendu; llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] [RFC][SLP] Let's turn -slp-vectorize-hor on by default