similar to: 4kB sector size HDDs

I have trouble finding definitive information about this. I am considering the use of SME 7.5.1 (centOS based) for my server needs, but I do want to use ZFS and I thus far I have only found information about the ZFS-Fuse implementation and unclear hints that there is another way. Phoronix reported that http://kqinfotech.com/ would release some form of ZFS for the kernel but I have found nothing.

On Wed, 2017-02-15 at 16:50 -0500, Dawid Zamirski wrote: > On Wed, 2017-02-15 at 21:14 +0000, Richard W.M. Jones wrote: > > On Wed, Feb 15, 2017 at 02:28:41PM -0500, Dawid Zamirski wrote: > > > Correct, however there's also no guarantee that seeking by 4k in > > > "garbage" data would not land you in registry data that happens > > > to > >

On Wed, Feb 15, 2017 at 02:28:41PM -0500, Dawid Zamirski wrote: > Correct, however there's also no guarantee that seeking by 4k in > "garbage" data would not land you in registry data that happens to > evaluate to "hbin" as well. That's why I put "hbin" offset validation > check couple of lines below to make sure that the "hbin" we found

On Wed, Feb 15, 2017 at 01:48:29PM -0500, Dawid Zamirski wrote: > On Wed, 2017-02-15 at 16:54 +0000, Richard W.M. Jones wrote: > > On Tue, Feb 14, 2017 at 12:05:20PM -0500, Dawid Zamirski wrote: > > > * hivex_open: when looping over hbin sections (aka pages), handle a > > >   case where following hbin section may not begin at exactly at the > > > end > >

hi, we use dovecot 2.2.13, and we've lately started using maildir quota (previously fs quota was used, right now it's "quota = maildir:User quota" changed from "quota = fs:User quota:user:inode_per_mail"). When the change was applied we didn't manually forced generating maildirsize files. So, when the first deliver happens (or the file grows larger then 5KB)

On Wed, Feb 08, 2017 at 04:36:31PM -0500, Dawid Zamirski wrote: > There are some corrupted registry files that have invalid hbin cells > but are still readable. This patch makes the following changes: > > * hivex_open - do not abort with complete failure if we run across a > block with invalid size (unless it's the root block). Instead just > log the event, and move on.

On Tue, Feb 14, 2017 at 12:05:20PM -0500, Dawid Zamirski wrote: > * hivex_open: when looping over hbin sections (aka pages), handle a > case where following hbin section may not begin at exactly at the end > of previous one. If this happens, scan the page section until next > one is found and validate it by checking declared offset with actual > one - if they match, all is

Hi, As a way to learn LLVM, I'm trying to write a backend for the Microchip PIC18 8-bit microcontroller. On this device, the hardware stack is very small and is used only for storing function return addresses. A "real" software stack implementation is not very efficient because of the limited instruction set, so for all the non-reentrant functions I've decided to use a similar

Hello! I want to connect computers with windows xp (pro/home) to a one computer linux (with samba). I want to every user who want to use his/her account data may use any of the computers in the office and have theys personal data (in any pleace in the office) (domain or something, i don't know). I have a little problem with a how to plan and configure all of that and i am thinking if it

Hello, The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be

Hi list, I googled around but couldn''t find anything on whether someone has good or bad experiences with the Caviar *Blue* drives? I saw in the archives Caviar Blacks are *not* recommended for ZFS arrays (excluding apparently RE3 and RE4?). Specifically I''m looking to buy Western Digital Caviar Blue WD10EALS 1TB drives [1]. Does anyone have any experience with these drives? If

I am following the examples section 9.3 in the "Samba 3 By Example" book. I can SSH onto the samba server as an AD user but I cant mount a samba share. If I run wbinfo -u or -g it shows the users and groups BUT it doesn't show the short domain name, also if I run the getent commands they shouw details but no domain name. Can anyone offer any suggestions as to what may be wrong.

On Fri, 2016-02-05 at 18:08 +0000, Richard W.M. Jones wrote: > On Fri, Feb 05, 2016 at 12:15:32PM -0500, Dawid Zamirski wrote: > > This patch updates the guestfs_inspect_get_drive_mappings API call > > to > > also return drive letters for GPT paritions. Previously this worked > > only for MBR partitions. This is achieved by matching the GPT > > partition > >

On Thu, 2017-02-16 at 08:43 +0000, Richard W.M. Jones wrote: > On Wed, Feb 15, 2017 at 10:59:33PM +0000, Richard W.M. Jones wrote: > > > > OK, I ended up turning the warning off.  It appears from the > > info file that the warning is about GCC not being able to make > > an optimization, not a bug in the code. > > > > However I do have a more substantial

Hi everybody. Hardware: Several computers with Asus P/I-P55t2P4S motherboard, CPU Pentium MMX and K6-2/3, 128 to 384 MB RAM, Award 4.51PG Bios, Hard disks from 8 GB to 123.5 GB Realtek 8139D based NICs with PXE Boot-Proms PXELINUX 2.06 / MEMDISK 2.06: - fails to boot Compaq PC-DOS 3.31 PXELINUX 2.08 - succeeds to boot Compaq PC-DOS 3.31 with 0, 1, 2 and 3 hdds installed in

Dear gurus, Three DELL SC430s were purchased by my company a few months back and I've been told that when they spoke with the DELL representatives, they were informed that these servers were fully RHEL 4.0 compatible. Specs of the servers:- - Pentium 4 - 2.8 GHz - 1 GB RAM - 2x 250GB SATA HDDs I tried installing CentOS 4.0 on it but it doesn't seem to be able to detect any hard

I believe I've posted before about one of the speed issues we were having, of backups taking many, many hours that should *not* take that long. My manager and I finally nailed it down to the h/d itself. Identical boxes, and he tried a backup of one system which took under two hours, while the same regular one rand nearly six. I'd been googling on and off for weeks, and this morning, ran

Hi Everyone, I am stack between two identical systems (2U Twin2, 4 nodes, SuperMicro) servers that have the same exact specs except for HDDs. These nodes will all either have Asterisk installed with CentOS or will have Asterisk install in virtual environment. Option 1: *12* x 3.5" HDD (3 HDDs per node) Option 2: *24* x 2.5" HDD (6 HDDs per node) **both options come to the same price.

How can I tell wich HDD to swap, when the "cat /proc/mdstat" says one HDD of the RAID1 array has died? Does the HDD's has some serial numbers, that I can see in "reality", and I can get that number from e.g.: a commands output? How could I know wich HDD to swap in e.g.: a RAID1 array? thank you -------------- next part -------------- An HTML attachment

The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at