On Fri, May 22, 2020 at 5:40 PM antlists wrote:
>
> On 22/05/2020 19:23, Rich Freeman wrote:
> > A big problem with drive-managed SMR is that it basically has to
> > assume the OS is dumb, which means most writes are in-place with no
> > trims, assuming the drive even supports trim.
>
> I think
On 22/05/2020 19:23, Rich Freeman wrote:
A big problem with drive-managed SMR is that it basically has to
assume the OS is dumb, which means most writes are in-place with no
trims, assuming the drive even supports trim.
I think the problem with the current WD Reds is, in part, that the ATA-4
On Fri, May 22, 2020 at 04:17:24PM +0100, antlists wrote:
> If I understand what you are attempting correctly (not a given!) then what
> you are trying won't work. You're confusing multiple *folders* with multiple
> *users*.
Sorry, my original e-mail was quite nondescript. Consider that I have
On Fri, May 22, 2020 at 2:08 PM antlists wrote:
>
> So what you could do is allocate one zone of CMR to every four or five
> zones of SMR and just reshingle each SMR as the CMR filled up. The
> important point is that zones can switch from CMR cache to SMR filling
> up, to full SMR zones decaying
On 22/05/2020 18:20, Rich Freeman wrote:
On Fri, May 22, 2020 at 12:47 PM antlists wrote:
What puzzles me (or rather, it doesn't, it's just cost cutting), is why
you need a *dedicated* cache zone anyway.
Stick a left-shift register between the LBA track and the hard drive,
and by switching
Rich Freeman wrote:
> On Fri, May 22, 2020 at 12:15 PM Dale wrote:
>> The thing about the one I have now in use by LVM for /home, one is SMR and
>> one is PMR. Even if the OS is aware, does it even know which drive the data
>> is going to end up being stored on? I'm pretty sure since the PMR
On Fri, May 22, 2020 at 12:47 PM antlists wrote:
>
> What puzzles me (or rather, it doesn't, it's just cost cutting), is why
> you need a *dedicated* cache zone anyway.
>
> Stick a left-shift register between the LBA track and the hard drive,
> and by switching this on you write to tracks
On Fri, May 22, 2020 at 12:15 PM Dale wrote:
>
> The thing about the one I have now in use by LVM for /home, one is SMR and
> one is PMR. Even if the OS is aware, does it even know which drive the data
> is going to end up being stored on? I'm pretty sure since the PMR drive was
> in use
On 22/05/2020 16:43, Rich Freeman wrote:
On Fri, May 22, 2020 at 11:32 AM Michael wrote:
An interesting article mentioning WD Red NAS drives which may actually be SMRs
and how latency increases when cached writes need to be transferred into SMR
blocks.
Yeah, there is a lot of background on
Rich Freeman wrote:
> On Fri, May 22, 2020 at 11:32 AM Michael wrote:
>> An interesting article mentioning WD Red NAS drives which may actually be
>> SMRs
>> and how latency increases when cached writes need to be transferred into SMR
>> blocks.
> Yeah, there is a lot of background on this
On Fri, May 22, 2020 at 11:32 AM Michael wrote:
>
> An interesting article mentioning WD Red NAS drives which may actually be SMRs
> and how latency increases when cached writes need to be transferred into SMR
> blocks.
Yeah, there is a lot of background on this stuff.
You should view a
On Sunday, 10 May 2020 21:52:54 BST antlists wrote:
> On 10/05/2020 20:11, Rich Freeman wrote:
> >> I did find a WD Red 8TB drive. It costs a good bit more. It's a good
> >> deal but still costs more. I'm going to keep looking. Eventually I'll
> >> either spend the money on the drive or find a
On 21/05/2020 21:14, Ashley Dixon wrote:
Hello,
I am attempting to set up sub-addressing on my Courier mail server, allowing
senders to directly deliver messages to a particular folder in my mailbox. For
example, I want to provide my University with the address
On 5/21/20 4:14 PM, Ashley Dixon wrote:
Hello,
I am attempting to set up sub-addressing on my Courier mail server, allowing
senders to directly deliver messages to a particular folder in my mailbox. For
example, I want to provide my University with the address
On 21/05/2020 20:25, Ashley Dixon wrote:
On Thu, May 21, 2020 at 08:13:38PM +0100, Ján Zahornadský wrote:
when updating the system today, a new revision of nvidia-drivers ebuild
fails with
ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf
15 matches
Mail list logo