search for: 512byte

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem

...le to add a parameter/argument to syslinux.com/syslinux.exe to specify a file? currently it's something like SYSLINUX A: I'd like the following also to be possible: SYSLINUX A: A:\SYSLINUX.BIN It still copies LDLINUX.BIN to A:, but writes the generated bootsector intended for drive A: to a 512byte user-specified file Perhaps to allow both at the same time even SYSLINUX A: A: A:\SYSLINUX.BIN could be possible SYSLINUX [place-to-copy-ldlinux.bin-to] [place(s) where to put bootsector(file)] I'm supporting 8086+ instead of 386+, so I need another bootloader (called MetaKern) before SYSLINU...

...39;t (ungzip failed); looks like an initrd The same .cpio archive works if I don't gzip it. I stuck a bunch of debug statements into the gunzip function to see what was happening. The core of the problem is in the init/initramfs.c, the populate_rootfs and unpack_to_rootfs functions. I see a 512byte image at &__initramfs_start being uncompressed. Then I see my image during the dry-run inside the "if (initrd_start)" block, which gets checked correctly with gunzip(). The problem is that the same call to unpack_to_rootfs() finds another header, which is broken. I solved the probl...

...eate a separate swap partition of memory x 2 (=2Gb). Then the LVM partition has two ext3 partitions, one for / around 12Gb, and the other for /home as the rest. The drive is a 60Gb drive, so I might make / bigger: ext3 /boot 100mb swap 2Gb LVM Rest of drive (to 512byte multiple) ext3 / 12Gb ext3 /home rest of LVM

Well, now that I''ve figured out that network booting XCP is not really going to be feasible, I''m moving on to my next option: flash media installation. The systems that I purchased have SDHC slots on them, so I figured I''d attempt to install XCP to one of these cards. I had already read that there''s a minimum disk size in the installer (apparently 12 GB in

...tic management no no media status notification no no power-up in Standby yes no write-read-verify yes no 0/0x0 unload yes yes free-fall no no data set management (DSM/TRIM) yes DSM - max 512byte blocks yes 8 DSM - deterministic read yes any value Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of...

I am bumping this thread because I too have the same question ... can I put modern 3TB disks (hitachi deskstars) into an old x4500 ? If not, would the x4540 accept them ? -- This message posted from opensolaris.org

Hi We have a number offices accommodating 4-6 people each hence it is very important for PBX to be fanless and silent. We have been looking at using IDE flash disks also called DOM. The performance tests we have done so far satisfy our requirements, however we are concerned with DOM durability. We have installed debian and vanilla asterisk on 1GB DOM. All seems to work fine at the moment however

Hi people... Here we use Xen 4 with Debian Lenny... We''re using kernel 2.6.31.13 pvops... As a storage system, we use AoE devices... So, we installed VM''s on AoE partition... The "NAS" server is a Intel based baremetal with SATA hard disc... However, sometime I feeling that VM''s is so slow... Also, all VM has GPLPV drivers installed... So, I am thing about

Hi all, I stumbled over a curious thing. The Linux tools "df" and "du" aren't working correctly on an OCFS2 filesystem. "df" shows approx. twice the size as there is on the volume. Here how I found out about this issue: - same dir(a few files more in OCFS but the files are ca. 12 kB in size), first on XFS second on the OCFS volume # du -ms

(I've already sent this message to Ted Ts'o directly. I should have sent it to this list first but I didn't know about it until today. My apologies to Ted.) Last Friday a system that I just inherited refused to mount a file system that had been working fine for about 6 months. This is on a Scientific Linux 4.3 system using a 2.6.9 kernel. This is another Linux distribution based on

...round that Windows requires? -- -Gene A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing? > here is the preparation log for the attached bootsectors: > > this is a traditional HDD having 512byte sectors > on a traditional BIOS/MBR system > using LBA > > existing partition created by windows 8.1 > -this is primary partition3 of a multipartitioned HDD > -which displays same behavior as partition1 of a single-volume HDD > bootsector in place at desired sector 19595264 &gt...

Well this is a new one.... Illumos/Openindiana let me add a device as a hot spare that evidently has a different sector alignment than all of the other drives in the array. So now I''m at the point that I /need/ a hot spare and it doesn''t look like I have it. And, worse, the other spares I have are all the same model as said hot spare. Is there anything I can do with this or

...hat have requests on a given + underlying block device use up their tokens. + + The weight policy lets dm-ioband consume one token per one I/O request. + The weight-iosize policy lets dm-ioband consume one token per one I/O + sector, for example, one I/O request which consists of 4Kbytes (512bytes * + 8 sectors) read consumes 8 tokens. + + With this approach, a job running on the ioband group with large weight + is guaranteed a wide I/O bandwidth. + + -------------------------------------------------------------------------- + + range-bw policy + + range-bw means the predicab...

...hat have requests on a given + underlying block device use up their tokens. + + The weight policy lets dm-ioband consume one token per one I/O request. + The weight-iosize policy lets dm-ioband consume one token per one I/O + sector, for example, one I/O request which consists of 4Kbytes (512bytes * + 8 sectors) read consumes 8 tokens. + + With this approach, a job running on the ioband group with large weight + is guaranteed a wide I/O bandwidth. + + -------------------------------------------------------------------------- + + range-bw policy + + range-bw means the predicab...

...hat have requests on a given + underlying block device use up their tokens. + + The weight policy lets dm-ioband consume one token per one I/O request. + The weight-iosize policy lets dm-ioband consume one token per one I/O + sector, for example, one I/O request which consists of 4Kbytes (512bytes * + 8 sectors) read consumes 8 tokens. + + With this approach, a job running on the ioband group with large weight + is guaranteed a wide I/O bandwidth. + + -------------------------------------------------------------------------- + + range-bw policy + + range-bw means the predicab...

...hat have requests on a given + underlying block device use up their tokens. + + The weight policy lets dm-ioband consume one token per one I/O request. + The weight-iosize policy lets dm-ioband consume one token per one I/O + sector, for example, one I/O request which consists of 4Kbytes (512bytes * + 8 sectors) read consumes 8 tokens. + + With this approach, a job running on the ioband group with large weight + is guaranteed a wide I/O bandwidth. + + -------------------------------------------------------------------------- + + range-bw policy + + range-bw means the predicab...

...hat have requests on a given + underlying block device use up their tokens. + + The weight policy lets dm-ioband consume one token per one I/O request. + The weight-iosize policy lets dm-ioband consume one token per one I/O + sector, for example, one I/O request which consists of 4Kbytes (512bytes * + 8 sectors) read consumes 8 tokens. + + With this approach, a job running on the ioband group with large weight + is guaranteed a wide I/O bandwidth. + + -------------------------------------------------------------------------- + + range-bw policy + + range-bw means the predicab...

...hat have requests on a given + underlying block device use up their tokens. + + The weight policy lets dm-ioband consume one token per one I/O request. + The weight-iosize policy lets dm-ioband consume one token per one I/O + sector, for example, one I/O request which consists of 4Kbytes (512bytes * + 8 sectors) read consumes 8 tokens. + + With this approach, a job running on the ioband group with large weight + is guaranteed a wide I/O bandwidth. + + -------------------------------------------------------------------------- + + range-bw policy + + range-bw means the predicab...

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at