Skip to content

.nilfs file created by mkfs.nilfs2 #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sodface opened this issue Oct 8, 2022 · 2 comments
Closed

.nilfs file created by mkfs.nilfs2 #21

sodface opened this issue Oct 8, 2022 · 2 comments

Comments

@sodface
Copy link

sodface commented Oct 8, 2022

This commit eliminated the creation of the .nilfs file:
2c66e06

The current version and all versions since the above change of sbin/mkfs/mkfs.c in this repo do not contain the code (as expected) but the nilfs-utils-2.2.9.tar.bz2 does and indeed the .nilfs file is being created by mkfs.nilfs2 built from that source archive.

Since the source archive was created recently (long after the change) this seems unexpected?

// edit

My apologies, the code is still present in the 2.2.y branch which explains why it's in the 2.2.9 release. What should distros be packaging? The 2.2.9 release or current master?

@konis
Copy link
Member

konis commented Oct 9, 2022

The .nilfs file is an obsolete file and no longer needed.
That file was initially used for exclusive control of garbage collection (cleaner) in user space, but has been replaced with a different method a long time ago. The removal of the file in master branch is intentional.

I could have removed it at the 2.2.9 release, but I didn't want to make much changes other than build issues in 2.2.9, so I put it on hold. If I publish the next maintenance release (i.e. 2.2.10), I will remove it there to put an end to this matter. Or if we can release 2.3.0 from the master branch, it will be resolved naturally.

Bascially 2.2.y is the branch for maintenance releases and the master branch is the branch for the next major release. (That's the reason for the difference whether that file exists or not.)

Although the master branch is stable enough, distros should preferably package the latest version of the 2.2.y branch, ie 2.2.9 for now because 2.3.0 hasn't been released yet.

I'm sorry that the 2.3.0 release has been stalled because I haven't been able to devote myself to this task for a long time. Recently, I have resumed NILFS activities, but there are many problems in the kernel module that need to be fixed and I prioritize solving them. So, I haven't touched the development of the master branch yet. I believe that once the kernel module has settled down, I will be able to resume this activity as well.

Thank you.

@sodface
Copy link
Author

sodface commented Oct 9, 2022

Thank you for the response and I understand everything you stated. I maintain the nilfs-utils package for Alpine Linux and will keep it at 2.2.9 per your recommendation. It is welcome news that you are finding time to work on NILFS, thank you for your effort in maintaining this unique and useful filesystem!

@sodface sodface closed this as completed Oct 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy