similar to: Error: value too large for defined data type

i have recently rebuilt dovecot on my mail server as i wanted to add SSL support for it. well, my OpenSSL libs are 64-bit, so what they hey, i'll build dovecot 64-bit as well. worked just fine, no issues at all. the setup is: Solaris 9/SPARC Sun C compiler Dovecot 0.99.14 after rebuilding it 64-bit, i now have a small problem however. I cannot save messages to IMAP folders from Mail.app

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

I''m trying to figure out what the CURRENT requirements are for configuring the xVM domains to start at boot-time and stop on shutdown. The closest to current I''ve seen is http://opensolaris.org/os/community/xen/docs/xVM_lowres.pdf which does not address the problem, and http://opensolaris.org/os/community/xen/docs/xvm-ktde-20070917.pdf which states: *

During boot, I get the following error: Nov 16 09:16:41 sol11 svc.startd[7]: [ID 652011 daemon.warning] svc:/system xvm/store:default: Method "/lib/svc/method/xenstored start" failed with exit status 96. Nov 16 09:16:41 sol11 svc.startd[7]: [ID 748625 daemon.error] system/xvm/store:default misconfigured: transitioned to maintenance (see ''svcs -xv'' for details) It

Hello, i try to use samba as backup solution for our NT4 servers. At 03:05 every night we automatically shut down the servers, boot DOS and create with Symantec Ghost offline a disaster recovery image of the NT4 SCSI disks (NTFS) on a separate DOS IDE disk (fat32). The down (aka DOS) time is about 15-20 minutes. Then the machine boots with NT4 again. The image (one or two files with max 2G each)

hi folks, is there a straightforward or well-documented way to migrate my physical sxce snv_115 (x64) system into an xvm ? searching for "p2v" in an opensolaris context seems to pick up a few hits on zones, but nothing obvious relating to xvm on opensolaris for what it''s worth the host system is opensolaris (2010.02 snv_126), but i''m hoping that''s not very

> Hi Ady, > > On 2016.02.25 02:08, Ady via Syslinux wrote: > > There is an "extra" sector, in comparison to... what exactly? > > Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size > had an extra sector compared to minfatsize, when of course I meant the > opposite (the Large FAT32 has one less sector than the minfatsize >

> > instead of _always_ adding "+1" (which would be > > incorrect and inefficient from the point of view of the resulting > > allocatable size). > > I carefully considered this, and I dispute the fact that this is incorrect. > (snip) > Still, I won't prevent you (or anybody else interested) to provide a > proper formula if you want. ;) >

Hi, Is there any way to make Wine report a filesystem type other than FAT32 to applications (specifically, NTFS)? The reason I ask is that VirtualDub (a video postprocessing package) refuses to allow creation of files greater than 4GB on what it thinks are FAT32 drives. I know it works perfectly with really big files (>50GB) on NTFS because I've used it on WinNT. Thanks Stephen

I was troubleshooting a problem we were having with some files not rsyncing properly over an nfs mount (the destination device is a snapserver (NAS) that did not have native ability to receive streaming rsync info, that's why we were doing this rsync over an NFS connection to the snapserver). Anyway, at first I thought this was just one of the quirks of the snapserver (it isn't

> When trying to installing Syslinux on a FAT32 drive formatted using > Ridgecrop's Large FAT32 formatting tool [1], the installer will bail due > to the minfatsize check, as there is an extra sector being used. This > fix addresses that. > > [1] http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm > The expression: "...as there is an extra sector being

I''ve been using a 5-disk raidZ for years on SXCE machine which I converted to OSOL. The only time I ever had zfs problems in SXCE was with snv_120, which was fixed. So, now I''m at OSOL snv_111b and I''m finding that scrub repairs errors on random disks. If I repeat the scrub, it will fix errors on other disks. Occasionally it runs cleanly. That it doesn''t

In the following text, I am about to use terms such as "inaccurate". I don't mean to question what some code does, but rather to compare the expressions against what I think is a more accurate one, in theory. I mean no disrespect, and I am not saying that developers are doing the wrong thing. In addition, of course I could be wrong (or type in incorrectly, or some formatting

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,

Can anyone answer if we will get zfs de-duplication before SXCE EOL? If possible also anser the same on encryption? Thanks -- This message posted from opensolaris.org

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,

On Tue, Jan 21, 2014 at 2:41 PM, mike setzer <qualityana at sbcglobal.net> wrote: > hello Gene, > > good to get your message > > I have not seen a link to reply to a particular thread, > so I am replying to you right now > hopefully the thread can be made to look right, also I double posted since my connection was lost > right during the first posting. Sorry, I

Hi All I've just shifteed over to linux,form Windows.I 'm having 5 partations for use by my windows XP Professional and another one by linux.The partation table is as shown : ------------------------------------------------------------------------------------------------------------------------------------------ [root at localhost6 ~]# fdisk -l Disk /dev/hdc: 250.0 GB, 250059350016

I've rsynced two directory structures back and forth a few times. Its a desktop to external (portable) drive. And then back once mobile work has changed files and field work is done. On this last go around I expected a few files to be transferred maybe 15-20 but instead I'm seeing several thousand. No way most of those were changed. At least not data wise. It doesn't appear that