Andriy Gapon writes:
> on 18/07/2013 20:44 George Hartzell said the following:
> > Andriy Gapon writes:
> > > on 17/07/2013 23:47 George Hartzell said the following:
> > > > How should I move forward with this?
> > >
> > > Could you please try to reproduce this problem using a kernel bui
Andriy Gapon writes:
> on 18/07/2013 20:44 George Hartzell said the following:
> > Andriy Gapon writes:
> > > on 17/07/2013 23:47 George Hartzell said the following:
> > > > How should I move forward with this?
> > >
> > > Could you please try to reproduce this problem using a kernel bui
on 18/07/2013 20:44 George Hartzell said the following:
> Andriy Gapon writes:
> > on 17/07/2013 23:47 George Hartzell said the following:
> > > How should I move forward with this?
> >
> > Could you please try to reproduce this problem using a kernel built with
> > INVARIANTS options?
>
> I
George Hartzell writes:
>
> George Hartzell writes:
> > George Hartzell writes:
> > > [...]
> > > So, it would seem that there's something about the filesystem in which
> > > my home directory resides that contributes to the problem.
> > > [...]
> >
> > Another data point.
>
George Hartzell writes:
> George Hartzell writes:
> > [...]
> > So, it would seem that there's something about the filesystem in which
> > my home directory resides that contributes to the problem.
> > [...]
>
> Another data point.
>
> [...]
Yet another data point or three.
I took
George Hartzell writes:
> [...]
> So, it would seem that there's something about the filesystem in which
> my home directory resides that contributes to the problem.
> [...]
Another data point.
I just ran through my test case, saving the tagged and transcoded
files into /tmp, a zfs filesystem
Richard Todd writes:
> On Thu, Jul 18, 2013 at 11:40:51AM -0700, George Hartzell wrote:
> [...]
> > [...]
> > In my case I'd want to find a particular set of file size, offset, and
> > insertion size that triggers the problem and code up a c/c++ equiv. of
> > the
On Thu, Jul 18, 2013 at 11:40:51AM -0700, George Hartzell wrote:
> Removing the mmap support from those two routines seems to avoid the
> issue.
Aha.
> > If so, then the issue is triggered by one or both of those two routines;
> > hack them to print out the exact offsets used on each call and
I know how all not loving "me-too" emails, but I'll try :)
There's a rtorrent, which uses mmap. And I had cases (related to reboot),
where big files
(or average files in many-files torrents) appears with broken checksum
without any good reason.
Author of rtorrent not very politely always assume tha
Richard Todd writes:
> George Hartzell writes:
>
> > Hi All,
> >
> > I have what I think is a ZFS related bug.
> > [...]
>
> [summary: Picard seems to trigger an mmap consistency bug in ZFS].
>
> [...]
> Anyway, what I'd suggest is the following: see if my patch for py-mutagen
> disa
Andriy Gapon writes:
> on 17/07/2013 23:47 George Hartzell said the following:
> > How should I move forward with this?
>
> Could you please try to reproduce this problem using a kernel built with
> INVARIANTS options?
I added INVARIANT_SUPPORT and INVARIANTS options to the GENERIC
kernel, r
on 17/07/2013 23:47 George Hartzell said the following:
> How should I move forward with this?
Could you please try to reproduce this problem using a kernel built with
INVARIANTS options?
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http
George Hartzell writes:
> Hi All,
>
> I have what I think is a ZFS related bug. Unfortunately my simplest
> test case is a bit cumbersome and I haven't definitively proven that
> the problem is ZFS related.
> I'm hoping for some feedback on how to move forward.
>
> Quick background: I rip my CD
13 matches
Mail list logo
