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.

73
diana 

On September 5, 2023 11:31:26 AM MDT, John Holland <johnbholl...@icloud.com> 
wrote:
>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 they mostly at least purport to be some sort of intact file. How can I 
> determine what they are? Please don’t suggest that I manually use “file” and 
> then an appropriate program to examine each one in turn
>
>> On Sep 5, 2023, at 1:17 PM, Andreas Kähäri <andreas.kah...@abc.se> wrote:
>> 
>> 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
>>> shell.
>>> 
>>> 
>>> I eventually got fsck to mark the /home filesystem clean but it found >4000
>>> lost files that it moved to lost&found. I am not so experienced with this,
>>> running "file" on a few of them shows that they may be intact files but they
>>> have numeric names now.
>> [cut]
>> 
>> 
>> A regular external backup would have saved your data no matter what
>> filesystem you might have been using.  There are a few different backup
>> solutions available in the ports tree.  I use restic, both on OpenBSD
>> and macOS.
>> 
>> 
>> -- 
>> Andreas (Kusalananda) Kähäri
>> SciLifeLab, NBIS, ICM
>> Uppsala University, Sweden
>> 
>> .
>> 
>

Reply via email to