Re: large file system issues and rescue questions

Peter Hessler writes: > On 2024 Dec 10 (Tue) at 21:10:51 +0200 (+0200), Divan Santana wrote: > > :mount 3b3840fcdf524721.c /data > > you've basically guaranteed corruption of your disk. the 'c' partition > the entire disk, including all metadata. > > You'll want to create another partition with

Re: large file system issues and rescue questions

>> >> Secondly question, is it possible from the rescue environment to edit >> >> the real /etc/fstab file? Because it would be handy for me in some >> >> cases to do so without booting from the install image. >> >> >> > >> > I just double checked bsd.rd from amd64 snapshot, and it seems that both

Re: large file system issues and rescue questions

On Thu, 12 Dec 2024 10:39:24 +0100, Divan Santana wrote: > > Kirill A. Korinsky writes: > > > On Tue, 10 Dec 2024 20:10:51 +0100, > > Divan Santana wrote: > >> > >> Secondly question, is it possible from the rescue environment to edit > >> the real /etc/fstab file? Because it would be handy

Re: large file system issues and rescue questions

Kirill A. Korinsky writes: > On Tue, 10 Dec 2024 20:10:51 +0100, > Divan Santana wrote: >> >> Secondly question, is it possible from the rescue environment to edit >> the real /etc/fstab file? Because it would be handy for me in some >> cases to do so without booting from the install image. >>

Re: large file system issues and rescue questions

Otto Moerbeek writes: > On Tue, Dec 10, 2024 at 09:10:51PM +0200, Divan Santana wrote: > >> Greetings and happy December :) >> >> I have a 3.5TB ffs mounted at /data which is specified in fstab. >> >> When there is a power outage this file system corrupts (I'll install >> another UPS shortly).

Re: large file system issues and rescue questions

On Wed, Dec 11, 2024 at 02:24:16PM +0100, Peter Hessler wrote: > On 2024 Dec 10 (Tue) at 21:10:51 +0200 (+0200), Divan Santana wrote: > > :mount 3b3840fcdf524721.c /data > > you've basically guaranteed corruption of your disk. the 'c' partition > the entire disk, including all metadata. > > Yo

Re: large file system issues and rescue questions

On 2024 Dec 10 (Tue) at 21:10:51 +0200 (+0200), Divan Santana wrote: :mount 3b3840fcdf524721.c /data you've basically guaranteed corruption of your disk. the 'c' partition the entire disk, including all metadata. You'll want to create another partition with size * in a or d to have a good time.

Re: large file system issues and rescue questions

On Tue, Dec 10, 2024 at 09:10:51PM +0200, Divan Santana wrote: > Greetings and happy December :) > > I have a 3.5TB ffs mounted at /data which is specified in fstab. > > When there is a power outage this file system corrupts (I'll install > another UPS shortly). > > Is it possible to fsck_ffs a

Re: large file system issues and rescue questions

On 2024-12-10, Divan Santana wrote: > Greetings and happy December :) > > I have a 3.5TB ffs mounted at /data which is specified in fstab. > > When there is a power outage this file system corrupts (I'll install > another UPS shortly). > > Is it possible to fsck_ffs a 3.5TB file system from the bo

Re: large file system issues and rescue questions

On Tue, 10 Dec 2024 20:10:51 +0100, Divan Santana wrote: > > Secondly question, is it possible from the rescue environment to edit > the real /etc/fstab file? Because it would be handy for me in some > cases to do so without booting from the install image. > I just double checked bsd.rd from am

large file system issues and rescue questions

Greetings and happy December :) I have a 3.5TB ffs mounted at /data which is specified in fstab. When there is a power outage this file system corrupts (I'll install another UPS shortly). Is it possible to fsck_ffs a 3.5TB file system from the boot rescue environment? When I've tried before I'v

Re: Best practices mirroring large file-system hierarchies?

Per Google, most likely there's a symlink loop in the source. See mkdirat(2) (it refers to ELOOP). See also errno(2), which has: 31 EMLINK Too many links It also has 62 ELOOP Too many levels of symbolic links Your message has the text from EMLINK, but mkdirat only mentions ELOOP. That's not

Re: Best practices mirroring large file-system hierarchies?

Michael Lowery Wilson writes: > Greetings, > > My attempts at creating a local mirror of Project Gutenberg's ebooks > under OpenBSD 6.9 using openrsync following official instructions: > https://www.gutenberg.org/help/mirroring.html have been unsuccessful. > > Specifically I am using: > > openrs

Re: Best practices mirroring large file-system hierarchies?

On 2021-06-07, Michael Lowery Wilson wrote: > Greetings, > > My attempts at creating a local mirror of Project Gutenberg's ebooks under > OpenBSD 6.9 using openrsync following official instructions: > https://www.gutenberg.org/help/mirroring.html have been unsuccessful. > > Specifically I am usi

Best practices mirroring large file-system hierarchies?

Greetings, My attempts at creating a local mirror of Project Gutenberg's ebooks under OpenBSD 6.9 using openrsync following official instructions: https://www.gutenberg.org/help/mirroring.html have been unsuccessful. Specifically I am using: openrsync -av --del aleph.gutenberg.org::gutenberg

Re: large file system

- Original Message - | Is there anyone using openbsd for large file systems ? | For a large file system, nowadays, i mean 16 TB! | | Thanks on advance. | | You do not want to have a file system so large when using UFS. You would use a lot of memory and the file system check would

large file system

Is there anyone using openbsd for large file systems ? For a large file system, nowadays, i mean 16 TB! Thanks on advance.