On Thu, 28 Nov 2019, Adrian Zaugg wrote:
>
> On 08.11.19 17:13, g4sra via Dng wrote:
> > PS: Being Raspberry Pi specific, I do not know why Raspbian does not use
> > F2FS, but that does not exclude Devuan from using it.
>
> There are some alternatives to F2FS like UBIFS and a few others. As
On 08.11.19 17:13, g4sra via Dng wrote:
> PS: Being Raspberry Pi specific, I do not know why Raspbian does not use
> F2FS, but that does not exclude Devuan from using it.
There are some alternatives to F2FS like UBIFS and a few others. As it
is said thas FS that do wear levelling on their own
On Fri, Nov 15, 2019 at 04:52:50PM -0600, John Morris wrote:
> Can't use fstrim in the VMs because qemu / libvirt doesn't support it yet.
It does if you use virtio-scsi instead of virtio-blk; same for scsi
passthrough or even fake-hardware emulation of regular scsi.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀ A MAP07
On Thu, 2019-11-14 at 22:03 -0500, Steve Litt wrote:
> The piece of information I couldn't find in your (John Morris') data
> is
> how much of the 160GiB is consumed with data. It makes a big
> difference.
They have had most of their space written to at this point. The setup
is three physical
The piece of information I couldn't find in your (John Morris') data is
how much of the 160GiB is consumed with data. It makes a big difference.
Consider my SSD hosted root partition, which is 4 or 5 years old:
[slitt@mydesk ~]$ df -h /
Filesystem
On Wed, 2019-11-13 at 04:06 -0800, Bruce Ferrell wrote:
> Well, I was thinking more along the lines of the "early" failure rate
> for SSD and not so much the convenience of a thing as small as my baby
> finger nail with insane amounts of
> storage. I have active and still in use rotational media
On Wed, Nov 13, 2019 at 07:27:03PM -0500, Steve Litt wrote:
> On Tue, 12 Nov 2019 10:31:27 +0100
>
> Regarding eliminating the journal, you bring up a good point. But so
> did some other people arguing the opposite. I suggest an installation
> that gives the following choices:
>
> * Don't use a
On Tue, 12 Nov 2019 10:31:27 +0100
Edward Bartolo via Dng wrote:
> Hi all,
>
> The Raspberry Pi is very frequency used with an SD Card which is
> highly intolerant of frequent writes as these are limited. My first SD
> Card became read only after about six weeks with Devuan running. Using
>
On 11/13/19 12:26 AM, Edward Bartolo via Dng wrote:
Quote from Bruce Ferrel: "There are actually a couple of ways around
the SD wear issue, even though people seem to dearly LOVE SSDs with
the exact same issue;
1.) Use a USB drive.
2.) Somewhat more esoteric, PXE boot and run from an NFS
Quote from Bruce Ferrel: "There are actually a couple of ways around
the SD wear issue, even though people seem to dearly LOVE SSDs with
the exact same issue;
1.) Use a USB drive.
2.) Somewhat more esoteric, PXE boot and run from an NFS image."
[/Quote]
You are right, people love SD Cards, not
Anno domini 2019 Tue, 12 Nov 18:14:36 -0800
tom scripsit:
> On Tue, 12 Nov 2019 16:51:25 -0700
> Gregory Nowak wrote:
>
> > On Tue, Nov 12, 2019 at 11:58:06AM -0800, Bruce Ferrell wrote:
> > > There are actually a couple of ways around the SD wear issue, even
> > > though people seem to dearly
There is another option I think is worth looking into. There's been
word on Samsung adding another filesystem to the Linux kernel called
the Flash Friendly FileSystem (F2FS). Perhaps instead of debating
disabling the ext4 journal we could just replace it with F2FS?
--
On Tue, 12 Nov 2019 10:31:27 +0100
Edward Bartolo via Dng wrote:
> Hi all,
>
> The Raspberry Pi is very frequency used with an SD Card which is
> highly intolerant of frequent writes as these are limited. My first SD
> Card became read only after about six weeks with Devuan running. Using
>
On Tue, 12 Nov 2019 16:51:25 -0700
Gregory Nowak wrote:
> On Tue, Nov 12, 2019 at 11:58:06AM -0800, Bruce Ferrell wrote:
> > There are actually a couple of ways around the SD wear issue, even
> > though people seem to dearly LOVE SSDs with the exact same issue;
>
> I haven't seen anyone mention
On Tue, Nov 12, 2019 at 11:58:06AM -0800, Bruce Ferrell wrote:
> There are actually a couple of ways around the SD wear issue, even though
> people seem to dearly LOVE SSDs with the exact same issue;
I haven't seen anyone mention even once in this entire thread so far
that the rpi supports
On Tue, 12 Nov 2019, Simon Hobson wrote:
> Ah yes, to think that many of us routinely carry around in our pockets
> more storage, RAM, and CPU capacity than we could have dreamed of having
> access to back when I got into IT. Cue obligatory Four Yorkshiremen
> sketch :D
>
Jim Jackson wrote:
> (*) These pi's are a lot more powerfull than the Sun Sparc servers we had
> NFS serving user data to 60+ workstations back in the 00's :-)
Ah yes, to think that many of us routinely carry around in our pockets more
storage, RAM, and CPU capacity than we could have dreamed
On Tue, 12 Nov 2019, Edward Bartolo via Dng wrote:
> Needless to state, although it seems, it is actually needed for some
> people, the Raspberry Pi is not a full blown server, although it can
> be used by the hobbyist adolescent who wants to experiment and learn.
:-)
Like everything, it
On 11/11/19 5:06 PM, Steve Litt wrote:
On Sat, 9 Nov 2019 12:53:26 -0800
tom wrote:
On Fri, 8 Nov 2019 16:55:34 +0100
"Dr. Nikolaus Klepp" wrote:
Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
Joril via Dng scripsit:
On 08/11/19 16:21, g4sra via Dng wrote:
FYI: ext4 filesystem journaling
Hi all,
The Raspberry Pi is very frequency used with an SD Card which is
highly intolerant of frequent writes as these are limited. My first SD
Card became read only after about six weeks with Devuan running. Using
Raspbian, this issue did not repeat itself.
Needless to state, although it seems,
Anno domini 2019 Tue, 12 Nov 09:05:30 +0100
Adam Borowski scripsit:
> On Mon, Nov 11, 2019 at 08:06:26PM -0500, Steve Litt wrote:
> > > I really don't think data-loss is an acceptable compromise just to
> > > reduce wear.
> >
> > Lack of a journal doesn't necessarily mean data loss. It just
On Mon, Nov 11, 2019 at 08:06:26PM -0500, Steve Litt wrote:
> > I really don't think data-loss is an acceptable compromise just to
> > reduce wear.
>
> Lack of a journal doesn't necessarily mean data loss. It just means
> that you might need to run fsck.ext4 on the drive after unmounting.
>
On Sat, 9 Nov 2019 12:53:26 -0800
tom wrote:
> On Fri, 8 Nov 2019 16:55:34 +0100
> "Dr. Nikolaus Klepp" wrote:
>
> > Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
> > Joril via Dng scripsit:
> > > On 08/11/19 16:21, g4sra via Dng wrote:
> > > > FYI: ext4 filesystem journaling (and swap)
Dr. Nikolaus Klepp writes:
> Anno domini 2019 Sat, 9 Nov 20:16:40 -0800
> tom scripsit:
> [snip]
>> Because the whole point of my starting this thread was to provide
>> instructions on how to recover a system after the dataloss occurred. If
>> you would take the time to read the original post.
Anno domini 2019 Sat, 9 Nov 20:16:40 -0800
tom scripsit:
> On Sat, 9 Nov 2019 22:09:13 +
> g4sra via Dng wrote:
>
> > On 09/11/2019 20:53, tom wrote:
> > > On Fri, 8 Nov 2019 16:55:34 +0100
> > > "Dr. Nikolaus Klepp" wrote:
> > >
> > >> Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
> > >>
On Sat, 9 Nov 2019 22:09:13 +
g4sra via Dng wrote:
> On 09/11/2019 20:53, tom wrote:
> > On Fri, 8 Nov 2019 16:55:34 +0100
> > "Dr. Nikolaus Klepp" wrote:
> >
> >> Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
> >> Joril via Dng scripsit:
> >>> On 08/11/19 16:21, g4sra via Dng wrote:
>
On 09/11/2019 20:53, tom wrote:
> On Fri, 8 Nov 2019 16:55:34 +0100
> "Dr. Nikolaus Klepp" wrote:
>
>> Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
>> Joril via Dng scripsit:
>>> On 08/11/19 16:21, g4sra via Dng wrote:
FYI: ext4 filesystem journaling (and swap) *should* be disabled
by
Anno domini 2019 Sat, 9 Nov 12:53:26 -0800
tom scripsit:
> On Fri, 8 Nov 2019 16:55:34 +0100
> "Dr. Nikolaus Klepp" wrote:
>
> > Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
> > Joril via Dng scripsit:
> > > On 08/11/19 16:21, g4sra via Dng wrote:
> > > > FYI: ext4 filesystem journaling (and
On Fri, 8 Nov 2019 16:55:34 +0100
"Dr. Nikolaus Klepp" wrote:
> Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
> Joril via Dng scripsit:
> > On 08/11/19 16:21, g4sra via Dng wrote:
> > > FYI: ext4 filesystem journaling (and swap) *should* be disabled
> > > by default on SD\SDHC media.
> >
> > To
Am 2019-11-08 20:28, schrieb Adam Borowski:
I've had an eMMC card that survived 4 years of a constant I/O-bound
load
with more writes than reads, before starting to fail. On the other
hand,
you can kill a SD card within a day.
A nice example what you should NOT do with flash memory ;-)
On Fri, Nov 08, 2019 at 04:13:58PM +, g4sra via Dng wrote:
> On 08/11/2019 15:36, Joril via Dng wrote:
> > On 08/11/19 16:21, g4sra via Dng wrote:
> >> FYI: ext4 filesystem journaling (and swap) *should* be disabled by default
> >> on SD\SDHC media.
> >
> > To reduce wear?
> There is good
On 08/11/2019 15:36, Joril via Dng wrote:
> On 08/11/19 16:21, g4sra via Dng wrote:
>> FYI: ext4 filesystem journaling (and swap) *should* be disabled by default
>> on SD\SDHC media.
>
> To reduce wear?
There is good documentation 'out there' about how SD\SDHC Flash and Journaling
works.
The
Anno domini 2019 Fri, 8 Nov 16:36:24 +0100
Joril via Dng scripsit:
> On 08/11/19 16:21, g4sra via Dng wrote:
> > FYI: ext4 filesystem journaling (and swap) *should* be disabled by default
> > on SD\SDHC media.
>
> To reduce wear?
Yes.
> ___
> Dng
On 08/11/19 16:21, g4sra via Dng wrote:
FYI: ext4 filesystem journaling (and swap) *should* be disabled by default on
SD\SDHC media.
To reduce wear?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
FYI: ext4 filesystem journaling (and swap) *should* be disabled by default on
SD\SDHC media.
On 08/11/2019 14:46, Joril via Dng wrote:
> On 27/10/19 03:32, tom wrote:
>
>> The defaults on the linux kernel flags have the options
>> rootflags=noload. This has the effect of disabling ext4
On 27/10/19 03:32, tom wrote:
The defaults on the linux kernel flags have the options
rootflags=noload. This has the effect of disabling ext4 filesystem
journaling, checksumming, and all other safeguards.
In addition to that the root filesystem's parameters are set to always
disable filesystem
Hi,
I have been using the Raspberry Pi for a music player with an IQaudIO
DAC PRO card. First, I used Devuan, which very sadly, did not
recognize the DAC. After about 2 months of using Devuan, my SDCard,
was burnt: no more write cycles were allowed and it become read-only.
To correct this, and at
Hello,
I wanted to warn those of you using the Raspberry Pi or other aarch64
Devuan ASCII installs.
The defaults on the linux kernel flags have the options
rootflags=noload. This has the effect of disabling ext4 filesystem
journaling, checksumming, and all other safeguards.
In addition to that
38 matches
Mail list logo
