similar to: E2BIG

On Tue, Jan 22, 2019 at 04:43:31PM -0500, Michael Meyer wrote: > This line was accidentally removed in 77fe74fc, causing > bug #1145056 (Bugzilla) to resurface. > --- > lib/utf16.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/lib/utf16.c b/lib/utf16.c > index e099548..67fa996 100644 > --- a/lib/utf16.c > +++ b/lib/utf16.c > @@ -58,6 +58,7 @@

Just a quick fyi... We''ve recently added support for blktap along with support for managing virtual disks (disk file images). There are some difference from a linux dom0. This is available in b101 @ http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ This allows you to create and manage vmdk and vdi (Virtual Box) disk files. By default, virt-install will now use a vmdk vdisk when

This line was accidentally removed in 77fe74fc, causing bug #1145056 (Bugzilla) to resurface. --- lib/utf16.c | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/utf16.c b/lib/utf16.c index e099548..67fa996 100644 --- a/lib/utf16.c +++ b/lib/utf16.c @@ -58,6 +58,7 @@ _hivex_recode (hive_h *h, recode_type t, /* Reset errno here because we don't want to accidentally * return

Thanks Rich! Just curious, when's the next hivex release scheduled to be tagged? Best, Michael On Tue, Jan 22, 2019 at 5:22 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Jan 22, 2019 at 04:43:31PM -0500, Michael Meyer wrote: > > This line was accidentally removed in 77fe74fc, causing > > bug #1145056 (Bugzilla) to resurface. > > --- > >

Apparently the b89 xvm-src.tar.bz2 tar bz2 archive is corrupted / truncated on the b89 source download page: http://dlc.sun.com/osol/on/downloads/b89/ http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 In the past, the xvm-src.tar.bz2 file had a size of ~ 100 mbytes; with b89 the size of the downloadable archive is only 72 mbytes. And bzip2 complains: % bzip2 -tv

Saw this just come through for 8-current, 7-stable ought to have it in a week or so. I have not encountered the problem so I would not be able to judge if this fixes it. Patch here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c.diff?r1=1.27;r2=1.28 pjd 2008-03-15 23:23:04 UTC FreeBSD src repository Modified files:

Hello all... I''m seeing this behaviour in an old build (89), and i just want to hear from you if there is some known bug about it. I''m aware of the "picket fencing" problem, and that ZFS is not choosing right if write to slog is better or not (thinking if we have a better throughput from disks). But i did not find anything about 100% slog activity (~115MB/s) blocks

[adding NBD list] On 4/23/19 2:36 AM, Richard W.M. Jones wrote: > On Mon, Apr 22, 2019 at 07:50:22PM -0500, Eric Blake wrote: >> Previously, we were squashing EOVERFLOW into EINVAL; continue to do so >> at points in the protocol where the client may not be expecting >> EOVERFLOW. > > The protocol spec is unclear on whether EOVERFLOW can be returned in > cases other

On Tue, Apr 23, 2019 at 07:38:41AM -0500, Eric Blake wrote: > [adding NBD list] > > On 4/23/19 2:36 AM, Richard W.M. Jones wrote: > > On Mon, Apr 22, 2019 at 07:50:22PM -0500, Eric Blake wrote: > >> Previously, we were squashing EOVERFLOW into EINVAL; continue to do so > >> at points in the protocol where the client may not be expecting > >> EOVERFLOW.

I''m happy to announce that we have moved the xen-unstable.hg Solaris dom0 development out to the OpenSolaris community. For hard core developers, you can download, build, and run Solaris dom0 and xen-unstable bits following the instructions at the end of this post. We are currently sync''d up to changeset #17644 (~May 15th). Hopefully we will sync up with xen-unstable.hg every

Hello all.. I did some tests to understand the behaviour of ZFS and slog (SSD), and for understand the workload i did implement a simple software to visualize the data blocks (read/write). I''m posting here the link in the case somebody wants to try it. http://www.eall.com.br/blog/?p=906 Thanks a lot for your time. Leal [http://www.eall.com.br/blog] -- This message posted from

Previously, we were squashing EOVERFLOW into EINVAL; continue to do so at points in the protocol where the client may not be expecting EOVERFLOW. Signed-off-by: Eric Blake <eblake@redhat.com> --- server/protocol.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/server/protocol.c b/server/protocol.c index a52bb56..0a9f73c 100644 --- a/server/protocol.c

Hello all, First off, i''m talking about a SXDE build 89. Sorry if that was discussed here before, but i did not find anything related on the archives, and i think is a "weird" issue... If i try to remove a specific file, i got: # rm file1 rm: file1: No such file or directory # rm -rf dir2 rm: Unable to remove directory dir2: Directory not empty Take a look: ------- cut

On Mon, Apr 22, 2019 at 07:50:22PM -0500, Eric Blake wrote: > Previously, we were squashing EOVERFLOW into EINVAL; continue to do so > at points in the protocol where the client may not be expecting > EOVERFLOW. > > Signed-off-by: Eric Blake <eblake@redhat.com> > --- > server/protocol.c | 16 ++++++++++------ > 1 file changed, 10 insertions(+), 6 deletions(-) >

https://bugs.freedesktop.org/show_bug.cgi?id=82704 Priority: medium Bug ID: 82704 Assignee: nouveau at lists.freedesktop.org Summary: kernel bug Severity: normal Classification: Unclassified OS: All Reporter: mattia.b89 at gmail.com Hardware: Other Status: NEW Version: 10.2

https://bugs.freedesktop.org/show_bug.cgi?id=84870 Bug ID: 84870 Summary: [NV50] [PBUS] write fault on boot Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Mapping of EOVERFLOW was missed in commit 6f8c8084. Mapping of EOPNOTSUPP is essential for .zero to trigger a fallback to .pwrite, missed in commit 6c0e00e9 (not to mention that it becomes a valid protocol failure once fast zero support is added). There is no Unix.ENOTSUP, or that would get the same treatment per commit abb2b47c. Preserving EROFS and EFBIG is useful because protocol.c

https://bugs.freedesktop.org/show_bug.cgi?id=78863 Priority: medium Bug ID: 78863 Assignee: nouveau at lists.freedesktop.org Summary: [nv50] errors when starts gnome-shell QA Contact: xorg-team at lists.x.org Severity: minor Classification: Unclassified OS: All Reporter: mattia.b89 at gmail.com

https://bugs.freedesktop.org/show_bug.cgi?id=79532 Priority: medium Bug ID: 79532 Assignee: nouveau at lists.freedesktop.org Summary: [NV50] errors with DMA PUSHER and idle channel Severity: normal Classification: Unclassified OS: All Reporter: mattia.b89 at gmail.com Hardware: Other Status:

In order to trigger a non-EIO failure, a script had to output _exactly_ 'EINVAL ' or similar, with one trailing space and no message, because we forgot to limit the length of the string comparison. Fix things to tolerate an error name without a message, as well as to be case-insensitive. Also, parse EOVERFLOW (missed in commit 6f8c8084). Signed-off-by: Eric Blake