On Fri, 27 Nov 2020 07:34:32 +0100
Gary Jennejohn wrote:
> On Thu, 26 Nov 2020 20:09:41 +0100
> Michael Gmelin wrote:
>
> > > On 26. Nov 2020, at 19:21, Gary Jennejohn wrote:
> > >
> > > ___On Thu, 26 Nov 2020 10:44:19 -0700
> > > Warner Losh wrote:
> > >
> > >>> On Thu, Nov 26, 2020
On Thu, 26 Nov 2020 20:09:41 +0100
Michael Gmelin wrote:
> > On 26. Nov 2020, at 19:21, Gary Jennejohn wrote:
> >
> > ___On Thu, 26 Nov 2020 10:44:19 -0700
> > Warner Losh wrote:
> >
> >>> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote:
> >>>
> >>>
> >>>
> >>> On Thu, 26 Nov 2020
On Thu, 26 Nov 2020 19:37:47 +0100
Dimitry Andric wrote:
> On 26 Nov 2020, at 19:21, Gary Jennejohn wrote:
> >
> > On Thu, 26 Nov 2020 10:44:19 -0700
> > Warner Losh wrote:
> ...
> >>> Example:
> >>>
> >>> /sbin/camcontrol standby /dev/da2 -v -t 1800
> >>
> >>
> >> Perfect! I've not
I have a Threadripper 2990WX system that I recently installed an AMD
Radeon Pro W5700 into. It runs fine unless I load the amdgpu driver, at
which point it panics several seconds after boot: I have enough time to
login and run a few commands, but even if I just leave it it'll panic.
I'm
Hi,
It seems the issue wasn't with the hardware or the connection.
I use mutt and it's the program that was slowing everything down,
and that was down to me using new mutt with my old config. The whole
pause for 5 seconds thing was due to it scanning gigabytes of email each
time it woke up. The
On Thu, Nov 26, 2020 at 07:37:47PM +0100, Dimitry Andric wrote:
In this case it's about ATA commands being passed though the USB bridge.
Does "camcontrol identify daX" fail in your case too?
I have used quite a bunch of different USB disks, mostly from WD or
Seagate, and these come with varying
> On 26. Nov 2020, at 19:21, Gary Jennejohn wrote:
>
> On Thu, 26 Nov 2020 10:44:19 -0700
> Warner Losh wrote:
>
>>> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote:
>>>
>>>
>>>
>>> On Thu, 26 Nov 2020 10:12:06 +0100
>>> Gary Jennejohn wrote:
>>>
On Thu, 26 Nov 2020 01:14:02
On 26 Nov 2020, at 19:21, Gary Jennejohn wrote:
>
> On Thu, 26 Nov 2020 10:44:19 -0700
> Warner Losh wrote:
...
>>> Example:
>>>
>>> /sbin/camcontrol standby /dev/da2 -v -t 1800
>>
>>
>> Perfect! I've not had to deal with sata disks that did this since the
>> ataidle days. I looked in
On Thu, 26 Nov 2020 10:44:19 -0700
Warner Losh wrote:
> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote:
>
> >
> >
> > On Thu, 26 Nov 2020 10:12:06 +0100
> > Gary Jennejohn wrote:
> >
> > > On Thu, 26 Nov 2020 01:14:02 -0700
> > > Warner Losh wrote:
> > >
> > > > On Thu, Nov 26,
On Thu, Nov 26, 2020 at 2:47 AM Dimitry Andric wrote:
> On 26 Nov 2020, at 01:10, tech-lists wrote:
> >
> > I have a usb3-connected harddrive. dmesg shows this:
> > [...]
> > da0: Fixed Direct Access SPC-4 SCSI device
> > [...]
> >
> > running current-r367806-arm64
> >
> > I think it might be
On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote:
>
>
> On Thu, 26 Nov 2020 10:12:06 +0100
> Gary Jennejohn wrote:
>
> > On Thu, 26 Nov 2020 01:14:02 -0700
> > Warner Losh wrote:
> >
> > > On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn
> > > wrote:
> > > > On Thu, 26 Nov 2020 00:10:40
On Thu, Nov 26, 2020 at 04:55:46PM +, Graham Perrin wrote:
> On 25/11/2020 17:35, Graham Perrin wrote:
> > ???
> > > root@momh167-gjp4-8570p:~ # zpool export Transcend
> > > cannot unmount '/Volumes/t500': umount failed
> > > root@momh167-gjp4-8570p:~ # umount /Volumes/t500
> > > umount:
On 25/11/2020 17:35, Graham Perrin wrote:
…
root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/Volumes/t500': umount failed
root@momh167-gjp4-8570p:~ # umount /Volumes/t500
umount: unmount of /Volumes/t500 failed: Device busy
root@momh167-gjp4-8570p:~ # lsof /Volumes/t500/
On Thu, 26 Nov 2020 10:12:06 +0100
Gary Jennejohn wrote:
> On Thu, 26 Nov 2020 01:14:02 -0700
> Warner Losh wrote:
>
> > On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn
> > wrote:
> > > On Thu, 26 Nov 2020 00:10:40 +
> > > tech-lists wrote:
> > >
> > > > Hi,
> > > >
> > > > I have
Hi!
> If the problem recurs: is it _ever_ sane to get nothing listed by lsof
> for a volume that can not be unmounted?
Use fstat -- this is part of the base system.
Maybe lsof does not catch every corner case ?
--
p...@opsec.eu+49 171 3101372Now what ?
On 26 Nov 2020, at 01:10, tech-lists wrote:
>
> I have a usb3-connected harddrive. dmesg shows this:
> [...]
> da0: Fixed Direct Access SPC-4 SCSI device
> [...]
>
> running current-r367806-arm64
>
> I think it might be auto-spinning-down or auto-sleeping. It's
> making initial interaction
On Thu, 26 Nov 2020 01:14:02 -0700
Warner Losh wrote:
> On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn wrote:
>
> > On Thu, 26 Nov 2020 00:10:40 +
> > tech-lists wrote:
> >
> > > Hi,
> > >
> > > I have a usb3-connected harddrive. dmesg shows this:
> > > [...]
> > > da0: Fixed Direct
On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn wrote:
> On Thu, 26 Nov 2020 00:10:40 +
> tech-lists wrote:
>
> > Hi,
> >
> > I have a usb3-connected harddrive. dmesg shows this:
> > [...]
> > da0: Fixed Direct Access SPC-4 SCSI device
> > [...]
> >
> > running current-r367806-arm64
> >
> >
On Thu, 26 Nov 2020 00:10:40 +
tech-lists wrote:
> Hi,
>
> I have a usb3-connected harddrive. dmesg shows this:
> [...]
> da0: Fixed Direct Access SPC-4 SCSI device
> [...]
>
> running current-r367806-arm64
>
> I think it might be auto-spinning-down or auto-sleeping. It's
> making
19 matches
Mail list logo
