I appreciate your taking the time to send that, and also thanks to Nick
Holland for posting earlier.
I'm writing this on the laptop in question.
It seems like, as with so many things, it's hard to know who to believe
and things are probably more nuanced than some would say. That's my way
Il 05/09/2023 14:54, John Holland ha scritto:
I just had a kernel panic when reloading a firefox tab pointed at
[...]
I've really been enjoying OpenBSD but I think it could really use a
journaled filesystem. I believe I have the correct options in fstab for
[...]
Journals *might* make
If push comes to shove, then the journaling file system may lose
more data, but it will be consistent. FFS will have written as much
as possible, sometimes without association with an inode, that's when
people encounter full lost+found directories.
Neither file system will correctly record the
On Wed, 6 Sep 2023 22:52:59 -0400
Nick Holland wrote:
> On 9/6/23 08:23, John Holland wrote:
> > Janne-
> >
> > Thanks for all that useful information.
> >
> > others- this is a thinkpad, that's not on all the time, so a cron
> > backup is not that good. I actually back up manually, currently
Den fre 8 sep. 2023 kl 03:47 skrev Steve Litt :
>
> My main computer is Void Linux. If I had to restore from backup every
> time the disks became mildly messed up, all my time would be spent
> backing up and restoring.
>
> I remember back in the 90's and early 00's before journalling every
>
My main computer is Void Linux. If I had to restore from backup every
time the disks became mildly messed up, all my time would be spent
backing up and restoring.
I remember back in the 90's and early 00's before journalling every
system crash was grounds for an ulcer.
I didn't know that the
On 9/6/23 08:23, John Holland wrote:
Janne-
Thanks for all that useful information.
others- this is a thinkpad, that's not on all the time, so a cron backup
is not that good. I actually back up manually, currently using "borg"
for that. I mostly just do email and web on it so there's probably
Janne-
Thanks for all that useful information.
others- this is a thinkpad, that's not on all the time, so a cron backup
is not that good. I actually back up manually, currently using "borg"
for that. I mostly just do email and web on it so there's probably
nothing serious lost. In a few days
On 2023-09-05, Ronan Viel wrote:
> What about backup?
> tar is ready to use.
The file formats currently supported by tar/pax don't work for all situations
(they can't store all filenames). For a base OS tool for backup, dump is
probably
a better choice.
Den tis 5 sep. 2023 kl 20:53 skrev John Holland :
>
> I have a backup that is at least 2 days old offsite at a friend’s house. It
> would be a bit of a pain to go retrieve it, but I could do that.
>
> Short of that, I have 4000+ files in lost+found with names like #1094827.
> What can I do with
A couple questions, did you look OpenBSD installer create the filesystems or
did you define a custom layout?
FWIW, you should have a pretty good idea what is in/home. I reckon you could
ignore lost+found contents as they would be related to some application running
when the fault occurred.
On 9/5/23 15:41, Rudolf Leitgeb wrote:
On Tue, 2023-09-05 at 14:16 -0400, John Holland wrote:
So this gave me the list of the files with what they seem to be in
groups. I think a lot of them are browser cache, jpegs, pngsI
looked
at some of the gzipped ones and they were web pages and css
On Tue, 2023-09-05 at 14:16 -0400, John Holland wrote:
> So this gave me the list of the files with what they seem to be in
> groups. I think a lot of them are browser cache, jpegs, pngsI
> looked
> at some of the gzipped ones and they were web pages and css files.
>
> There are some that
What about backup?
tar is ready to use.
Ronan
> Le 5 sept. 2023 à 16:12, John Holland a écrit :
>
> I just had a kernel panic when reloading a firefox tab pointed at facebook.
> After restarting, all the filesystems had errors but /home was particularly
> bad and caused the boot to stop
Sorry to kind of have an attitude with the "please don't suggest..."
-- I realized I could kind of do something like that.
as root, using bash I ran
#cd /home/lost+found
#echo "" > ~jholland/list; for i in `ls`; do file $i >> ~jholland/list; done
and then as me (jholland) I ran
cat list
I have a backup that is at least 2 days old offsite at a friend’s house. It
would be a bit of a pain to go retrieve it, but I could do that.
Short of that, I have 4000+ files in lost+found with names like #1094827. What
can I do with those? I tried running “file” on the first 50 via xargs and
On Tue, Sep 05, 2023 at 08:54:58AM -0400, John Holland wrote:
> I just had a kernel panic when reloading a firefox tab pointed at facebook.
> After restarting, all the filesystems had errors but /home was particularly
> bad and caused the boot to stop and prompt if I wanted to enter a root
>
I turned off softdep.
My backups aren't super-current so I don't see restoring from backup as
a good idea.
My point was, OpenBSD is behind some other OS's (most?) in the
filesystem department. I know, "patches welcome" :) ..
On 9/5/23 08:54, John Holland wrote:
I just had a kernel
As the book "OpenBSD Mastery Filesystems", Michael W Lucas, 2023 reads at
the side cover:
“Many users assume that their advanced filesystem is better than UFS
because they have so many features—snapshots, checksums, compression,
sophisticated caching algorithms, and so on—while all UFS has ever
John Holland writes:
> I just had a kernel panic when reloading a firefox tab pointed at
> facebook. After restarting, all the filesystems had errors but /home
> was particularly bad and caused the boot to stop and prompt if I
> wanted to enter a root shell.
>
>
> I eventually got fsck to mark
I just had a kernel panic when reloading a firefox tab pointed at
facebook. After restarting, all the filesystems had errors but /home was
particularly bad and caused the boot to stop and prompt if I wanted to
enter a root shell.
I eventually got fsck to mark the /home filesystem clean but
21 matches
Mail list logo
