search for: 4kib

Concern: Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks OS: CentOS 7.3 kernel Version: 3.10.0-514.el7.x86_64 Any IO (write) block size more than 4KiB is split in to number of 4KiB blocks on Centos 7.3 ( where I don'...

Concern: Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks OS: CentOS 7.3 kernel Version: 3.10.0-514.el7.x86_64 Any IO (write) block size more than 4KiB is split in to number of 4KiB blocks on Centos 7.3 ( where I don'...

...lem 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 about changing anything. -- Chris Murphy

While researching another issue unrelated to Syslinux, I found some mildly disturbing news that affects Syslinux. As HPA stated back on 2009-06-04, hard drive manufacturers are pushing towards a 4096B (4kiB; 4k) native sector size. They're calling it "Advanced Format Technology". It appears that WD (Western Digital; WDC) is the first with some products being released back in December and that Seagate just recently "jumped on the bandwagon". Seeing as HPA's mention of the...

Hi all, In RISC-V ISA, the range of conditional branches is within 4KiB. In current implementation, if the 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....

...10/5/20 10:20 PM, Kai Wang via llvm-dev wrote: > Correct the title. > > On Tue, Oct 6, 2020 at 11:11 AM Kai Wang <kai.wang at sifive.com > <mailto:kai.wang at sifive.com>> wrote: > > Hi all, > > In RISC-V ISA, the range of conditional branches is within 4KiB. > In current implementation, if the 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 &gt...

Hi, I am using dovecot (see dovecot -n output below) with metadata plugin in my own plugin. I want to insert and delete some large metadata (>4KiB). It seems, that the delete in a second call of my plugin smashes the file dovecot.dict in users dir: 1st call: *dovecot.dict is empty -delete metadata 1 -delete metadata 2 -insert metadata 1 ~8KiB -insert metadata 2 <1KiB *dovecot.dict contains two entries 2nd call: -delete metadata 1 -dele...

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

...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 about > changing anything. > Thanks everyone. That...

In data mercoledì 1 giugno 2016 02:04:33, Maros Zatko ha scritto: > --autosysroot option uses suggestions to user on how to mount filesystems > and change root suggested by --suggest option in virt-rescue. IMHO it should be called -i, like in the other tools, as what --autosysroot does is basically the same. > Commands are passed on kernel command line in format >

...ith as many firmwares as possible (so users should choose the values of 'h' and 's' accordingly and wisely). 6_ The resulting size of the isohybrid image should better be a multiple of 1MiB. 7_ The starting absolute offset of the resulting partition should better be a multiple of 4KiB. If the amount of cylinders would be a multiple of 2048, we would achieve #1 and #2 (and then #3), but not always #4. One possibility to help with #4 would be to loop the expected calculations of cylinders and resulting image size (please avoid reading the following as real code or calculation...

...h > of the boot command line of the Linux kernel is limited [1], and we are > already using more than 200 characters. What about escaping, have you found a counter-example? I don't see much problem with this limit either, have we run into an issue? It seems that max allowed size is about 4KiB (between 256 and 4KiB) and we're running a VM so I don't ever expect this to be a problem. > > An alternative approach with the cmdline could be passing like > guestfs_mount=/dev:/mntpoint:opts, which is slightly more complex to > parse, although provide a more strict interface...

Hello What is the largest file size that can be created on Linux ? is there any limitation ? Thanks

Hi, I am not an engineer or linux expert but I have been using syslinux to boot live disk filesets (extracted from iso's) residing on fat32 and NTFS volumes. In FAT32 there has been no problem going with larger cluster sizes up to the nominal maximum of 64K however, with NTFS it has not been possible to exceed the cluster size of 4096. With NTFS formatted using clusters of 8192 or larger,

So there seem to be some shortcomings in NTFS, still. 1. Symlinks are not supported. Proper symlinks exist in NTFS since Vista, so we should support them. 2. readdir() seems to be broken. I have been using the following test load to generate disk images: http://www.zytor.com/~hpa/syslinux/exttest-20140521.tar.xz Anyone who has been involved with the NTFS code who has a chance to take a

.../* Include 4 header length bytes */ + } + + if (h->msglvl >= 2) + fprintf (stderr, "hivex_value_data_cell_offset: Proceeding with indirect data.\n"); + + size_t data_offset = le32toh (vk->data_offset); + data_offset += 0x1000; /* Add 0x1000 because everything's off by 4KiB */ + if (!IS_VALID_BLOCK (h, data_offset)) { + if (h->msglvl >= 2) + fprintf (stderr, "hivex_value_data_cell_offset: returning EFAULT because data " + "offset is not a valid block (0x%zx)\n", + data_offset); + errno = EFAULT; + re...

.../* Include 4 header length bytes */ + } + + if (h->msglvl >= 2) + fprintf (stderr, "hivex_value_data_cell_offset: Proceeding with indirect data.\n"); + + size_t data_offset = le32toh (vk->data_offset); + data_offset += 0x1000; /* Add 0x1000 because everything's off by 4KiB */ + if (!IS_VALID_BLOCK (h, data_offset)) { + if (h->msglvl >= 2) + fprintf (stderr, "hivex_value_data_cell_offset: returning EFAULT because data " + "offset is not a valid block (0x%zx)\n", + data_offset); + errno = EFAULT; + re...

...ation for the value data. */ + if (len) + *len = 0; + return 0; + } else { + if (len) + *len = data_len + 4; /* Include 4 header length bytes */ + } + + size_t data_offset = le32toh (vk->data_offset); + data_offset += 0x1000; /* Add 0x1000 because everything's off by 4KiB */ + if (!IS_VALID_BLOCK (h, data_offset)) { + if (h->msglvl >= 2) + fprintf (stderr, "hivex_value_data_cell_offset: returning EFAULT because data " + "offset is not a valid block (0x%zx)\n", + data_offset); + errno = EFAULT; + re...

...ap(struct nvkm_vmm *vmm, u64 addr, u64 size) /*TODO: * - Avoid PT readback (for dma_unmap etc), this might end up being dealt * with inside HMM, which would be a lot nicer for us to deal with. - * - Multiple page sizes (particularly for huge page support). * - Support for systems without a 4KiB page size. */ int @@ -1220,8 +1219,8 @@ nvkm_vmm_pfn_map(struct nvkm_vmm *vmm, u8 shift, u64 addr, u64 size, u64 *pfn) /* Only support mapping where the page size of the incoming page * array matches a page size available for direct mapping. */ - while (page->shift && page-&gt...

...ylinder size of exactly 1 MiB gives much hope for success. But i understand that TAILS ISO production uses -h 255 -s 63 because the ISO grew above 1024 MiB. So cylinder size 1 MiB is not suitable. > 7_ The starting absolute offset of the resulting partition should > better be a multiple of 4KiB. This one is new to me. What can possibly happen if it is not fulfilled ? Well, isohybrid MBR partition 1 has to begin at LBA 0 in order to make it mountable, unless the ISO was produced by xorriso with -partition_offset to create a suitable second superblock and file tree. The advisable -partiti...