Re: "wireguard" implementation improperly merged and needs revert

2020-08-24 Thread Jason A. Donenfeld
Hi Nia, On Mon, Aug 24, 2020 at 5:57 PM nia wrote: > > Hi Jason, > > > We still need to protect the unique identity and reputation of > > WireGuard (our "brand"). This ensures that when people see the > > WireGuard name or logo, they know it is something we, the > > WireGuard developers, have

Re: fsck updating but not fixing filesystem

2020-08-24 Thread Michael Cheponis
Another data point: I can't remember ever when NTFS didn't come up clean after a crash, except of course when the disk itself was bad. "NTFS (NT File System) is a proprietary journaling file system developed by Microsoft. Starting with Windows NT 3.1, it is the default file system of the Windows

Re: "wireguard" implementation improperly merged and needs revert

2020-08-24 Thread nia
Hi Jason, > We still need to protect the unique identity and reputation of > WireGuard (our "brand"). This ensures that when people see the > WireGuard name or logo, they know it is something we, the > WireGuard developers, have worked on." Personally, I would be in favour of entirely rebranding

Re: fsck updating but not fixing filesystem

2020-08-24 Thread David Brownlee
On Mon, 24 Aug 2020 at 11:46, Mouse wrote: > > > I think the general consensus is that ffs can be inconsistent it ways > > fsck is unable to detect. > > ...much less fix. Yes. When I was doing the program that eventually > got massaged into resize_ffs, during development I had some filesystems

Re: fsck updating but not fixing filesystem

2020-08-24 Thread Mouse
> I think the general consensus is that ffs can be inconsistent it ways > fsck is unable to detect. ...much less fix. Yes. When I was doing the program that eventually got massaged into resize_ffs, during development I had some filesystems that were definitely corrupted but that fsck was happy

Re: fsck updating but not fixing filesystem

2020-08-24 Thread David Brownlee
On Sun, 23 Aug 2020 at 20:50, David Holland wrote: > > On Sun, Aug 23, 2020 at 08:14:31PM +0100, David Brownlee wrote: > > > > This time I've run fsck -f repeatedly and each time it marks the > > filesystem as clean, but the next run finds another issue. > > > > This is netbsd-9 amd64 stable

Re: fsck updating but not fixing filesystem

2020-08-24 Thread Edgar Fuß
> I have a reasonably large ffs filesystem (7.4GB, 35,459,874 files) I gues you mean 7.4TB? I remember (shudder) something similar, where the file server would panic (bad dir), fsck would fix some dirs (missing . or ..), the file server would panic ... rinse and repeat. Slightly short of me