Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
fda7b1ff
Commit
fda7b1ff
authored
Sep 28, 2024
by
Kent Overstreet
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
bcachefs: Create lost+found in correct snapshot
Signed-off-by:
Kent Overstreet
<
kent.overstreet@linux.dev
>
parent
20826fe6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
1 deletion
+7
-1
fs/bcachefs/fsck.c
fs/bcachefs/fsck.c
+7
-1
No files found.
fs/bcachefs/fsck.c
View file @
fda7b1ff
...
...
@@ -283,11 +283,17 @@ static int lookup_lostfound(struct btree_trans *trans, u32 snapshot,
return
ret
;
create_lostfound:
/*
* we always create lost+found in the root snapshot; we don't want
* different branches of the snapshot tree to have different lost+found
*/
snapshot
=
le32_to_cpu
(
st
.
root_snapshot
);
/*
* XXX: we could have a nicer log message here if we had a nice way to
* walk backpointers to print a path
*/
bch_notice
(
c
,
"creating lost+found in snapshot %u"
,
le32_to_cpu
(
st
.
root_snapshot
));
bch_notice
(
c
,
"creating lost+found in subvol %llu snapshot %u"
,
root_inum
.
subvol
,
le32_to_cpu
(
st
.
root_snapshot
));
u64
now
=
bch2_current_time
(
c
);
struct
btree_iter
lostfound_iter
=
{
NULL
};
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment