On Wed, Jul 01, 2020 at 09:07:54PM +0300, Staffan Thomén wrote:
> [ 184722.7286780] panic: lock error: Mutex: mutex_vector_enter,564: locking
> against myself: lock 0xc380065c6a40 cpu 0 lwp 0xc38007290aa0
> [ 184722.7286780] cpu0: Begin traceback...
> [ 184722.7286780] vpanic() at
Michael van Elst wrote:
On Mon, Jun 29, 2020 at 07:08:40PM +0300, Staffan Thomén wrote:
Chavdar Ivanov wrote:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
You are mapping a snapshot, it will be r/o.
You have to promote it first.
While it's true that the snapshot is r/o,
Michael van Elst wrote:
On Mon, Jun 29, 2020 at 07:08:40PM +0300, Staffan Thomén wrote:
Chavdar Ivanov wrote:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
You are mapping a snapshot, it will be r/o.
You have to promote it first.
While it's true that the snapshot is r/o,
On Mon, Jun 29, 2020 at 07:08:40PM +0300, Staffan Thomén wrote:
> Chavdar Ivanov wrote:
> > > # ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
> >
> > You are mapping a snapshot, it will be r/o.
> >
> > You have to promote it first.
>
> While it's true that the snapshot is r/o,
On Mon, 29 Jun 2020 at 17:08, Staffan Thomén wrote:
>
> Chavdar Ivanov wrote:
> >> # ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
> >
> > You are mapping a snapshot, it will be r/o.
> >
> > You have to promote it first.
>
> While it's true that the snapshot is r/o, surely it
Chavdar Ivanov wrote:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
You are mapping a snapshot, it will be r/o.
You have to promote it first.
While it's true that the snapshot is r/o, surely it shouldn't crash the system.
And is there a reason why ccd would require r/w?
On Mon, 29 Jun 2020 at 16:31, Staffan Thomén wrote:
>
> Michael van Elst wrote:
> > mlel...@serpens.de (Michael van Elst) writes:
> >
> >> mlel...@serpens.de (Michael van Elst) writes:
> >>> ci4...@gmail.com (Chavdar Ivanov) writes:
> # ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>
Michael van Elst wrote:
mlel...@serpens.de (Michael van Elst) writes:
mlel...@serpens.de (Michael van Elst) writes:
ci4...@gmail.com (Chavdar Ivanov) writes:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
That's a
Staffan Thomén writes:
> Greg Troxel wrote:
>> The other thing you can do is export the zvol snapshot via iscsi and use
>> an iscsi initiator on netbsd to mount it.
>
> I tried this particular flavor of filesystem/network pretzel and when
> a full backup ran, it worked for a while and then
Greg Troxel wrote:
The other thing you can do is export the zvol snapshot via iscsi and use
an iscsi initiator on netbsd to mount it.
I tried this particular flavor of filesystem/network pretzel and when a full
backup ran, it worked for a while and then killed my system DEAD. Not even the
On Sat, 29 Feb 2020 at 12:02, Michael van Elst wrote:
>
> ci4...@gmail.com (Chavdar Ivanov) writes:
>
> >> gdb points to spec_read:
> >>
> >> (gdb) target kvm netbsd.12.core
> >> 0x80224225 in cpu_reboot ()
> >> (gdb) bt
> >> #0 0x80224225 in cpu_reboot ()
> >> #1
ci4...@gmail.com (Chavdar Ivanov) writes:
>> gdb points to spec_read:
>>
>> (gdb) target kvm netbsd.12.core
>> 0x80224225 in cpu_reboot ()
>> (gdb) bt
>> #0 0x80224225 in cpu_reboot ()
>> #1 0x809fde2f in kern_reboot ()
>> #2 0x80a40299 in vpanic ()
>> #3
ci4...@gmail.com (Chavdar Ivanov) writes:
>addr2line didn't return anything (most likely I was invoking it wrong,
>I don't know).
You need to use the debug kernel (the netbsd.gdb file).
>gdb points to spec_read:
When used with netbsd.gdb you get more information. If you haven't
built it, you
One more attempt rebuilding zfs.kmod with the patch; now the ccd
device comes as expected:
...
ccd0: Concatenating 1 components
ccd0: /dev/zvol/dsk/tank/testu (4194304 blocks)
ccd0: total 4194304 blocks
...
but istgt still panics the system in exactly the same way.
On Sat, 29 Feb 2020 at 09:58,
On Sat, 29 Feb 2020 at 06:47, Michael van Elst wrote:
>
> On Fri, Feb 28, 2020 at 02:12:29PM +, Chavdar Ivanov wrote:
> > On Thu, 27 Feb 2020 at 20:41, Michael van Elst wrote:
> > > I've prepared a patch for -current that fixes this issue.
> > >
On Fri, Feb 28, 2020 at 02:12:29PM +, Chavdar Ivanov wrote:
> On Thu, 27 Feb 2020 at 20:41, Michael van Elst wrote:
> > I've prepared a patch for -current that fixes this issue.
> > http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/zvol.patch
>
> After applying the patch, rebuilding and
On Thu, 27 Feb 2020 at 20:41, Michael van Elst wrote:
>
> mlel...@serpens.de (Michael van Elst) writes:
>
> >mlel...@serpens.de (Michael van Elst) writes:
> >>ci4...@gmail.com (Chavdar Ivanov) writes:
> >>># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
> >>>ccdconfig: ioctl (CCDIOCSET):
mlel...@serpens.de (Michael van Elst) writes:
>mlel...@serpens.de (Michael van Elst) writes:
>>ci4...@gmail.com (Chavdar Ivanov) writes:
>>># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>>>ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
>That's a bug in the zfs driver.
On Thu, 27 Feb 2020 at 09:40, Michael van Elst wrote:
>
> mlel...@serpens.de (Michael van Elst) writes:
>
> >ci4...@gmail.com (Chavdar Ivanov) writes:
>
> >># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
> >>ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
>
> >>Apparently
mlel...@serpens.de (Michael van Elst) writes:
>ci4...@gmail.com (Chavdar Ivanov) writes:
>># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>>ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
>>Apparently not, in this case. I think the comments in the thread
>>suggest that
ci4...@gmail.com (Chavdar Ivanov) writes:
># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
>Apparently not, in this case. I think the comments in the thread
>suggest that already.
This is different. The ccd driver can use
On Wed, 26 Feb 2020 at 21:16, Michael van Elst wrote:
>
> ci4...@gmail.com (Chavdar Ivanov) writes:
>
> ># vnconfig -c vnd0 /dev/zvol/rdsk/pail/nbsd1
> >vnconfig: /dev/rvnd0: VNDIOCSET: Operation not supported
>
> If zvols aren't broken then this should work:
>
> ccdconfig -c ccd0 0
ci4...@gmail.com (Chavdar Ivanov) writes:
># vnconfig -c vnd0 /dev/zvol/rdsk/pail/nbsd1
>vnconfig: /dev/rvnd0: VNDIOCSET: Operation not supported
If zvols aren't broken then this should work:
ccdconfig -c ccd0 0 /dev/zvol/rdsk/pail/nbsd1
and then access /dev/ccd0[a-p]
--
--
g...@lexort.com (Greg Troxel) writes:
>Once you export a zvol via iscsi, then it makes sense to methat the system
>attaching it sees it as a disk drive.
Yes. The zvol is seen as a disk image.
>> I couldn't coax dkctl to create dk devices for the gpt on the volume,
>> and dkctl seems like a bit
Staffan Thomén writes:
> Replying to you both in one here..
>
> Chavdar Ivanov wrote:
>> On Wed, 26 Feb 2020 at 18:18, Greg Troxel wrote:
>>> Staffan Thomén writes:
I couldn't coax dkctl to create dk devices for the gpt on the volume,
and dkctl seems like a bit of a mismatch for
On Wed, 26 Feb 2020 at 19:28, Staffan Thomén wrote:
>
> Replying to you both in one here..
>
> Chavdar Ivanov wrote:
> > On Wed, 26 Feb 2020 at 18:18, Greg Troxel wrote:
> >> Staffan Thomén writes:
> >>> I couldn't coax dkctl to create dk devices for the gpt on the volume,
> >>> and dkctl seems
Replying to you both in one here..
Chavdar Ivanov wrote:
On Wed, 26 Feb 2020 at 18:18, Greg Troxel wrote:
Staffan Thomén writes:
I couldn't coax dkctl to create dk devices for the gpt on the volume,
and dkctl seems like a bit of a mismatch for creating arbitrary dk:s
anyway as it seems
On Wed, 26 Feb 2020 at 18:18, Greg Troxel wrote:
>
> Staffan Thomén writes:
>
> I should point out that I am underclued on zfs and windows both.
>
> > I recently wanted to set up backup of a (snapshot of a) zvol that I
> > had exported via iscsi to a windows machine, and got stumped because
> >
Staffan Thomén writes:
I should point out that I am underclued on zfs and windows both.
> I recently wanted to set up backup of a (snapshot of a) zvol that I
> had exported via iscsi to a windows machine, and got stumped because
> windows didn't just create a ntfs filesystem on the volume, it
Hey,
I recently wanted to set up backup of a (snapshot of a) zvol that I had
exported via iscsi to a windows machine, and got stumped because windows
didn't just create a ntfs filesystem on the volume, it also added a partition
table and so mount_ntfs and ntfs-3g couldn't find the filesystem
30 matches
Mail list logo
