https://bugzilla.kernel.org/show_bug.cgi?id=200951
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|-
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #17 from Chao Yu (c...@kernel.org) ---
Updated in below git link, :)
https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=f2fs-dev
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #16 from vice...@gmail.com ---
Hi,
thank you for being that fast!
I have tried it against v4.19-rc2
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=57361846b52bc686112da6ca5368d11210796804
but it does not
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #15 from Chao Yu (c...@kernel.org) ---
I've sent one patch for this issue, just cc your email, also you can find the
patch in below link[1], can you please try this patch to check whether it can
fix this issue?
[1] https://sourceforge
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #14 from vice...@gmail.com ---
This could explain why it fails on aarch64 but works on x86_64.
When this is tested on aarch64, the f2fs is the root FS, and the udev
rule is applied after mount because it is stored in the filesystemm it
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #13 from Chao Yu (c...@kernel.org) ---
(In reply to vicencb from comment #12)
> As stated in the bug description, there is an udev rule to set
Sorry, I missed this one... :(
> the provisioning_mode attribute to unmap. When searching
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #12 from vice...@gmail.com ---
As stated in the bug description, there is an udev rule to set
the provisioning_mode attribute to unmap. When searching for
this attribute name, i found this:
drivers/scsi/sd.c:749
blk_queue_max_discard
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #11 from Chao Yu (c...@kernel.org) ---
Actually, the problem here is during mount(), both blk_queue_discard(q) and
f2fs_sb_has_blkzoned(sbi) return false, so f2fs will skip allocating memory for
se->discard_map.
static inline bool f2
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #10 from vice...@gmail.com ---
Created attachment 278245
--> https://bugzilla.kernel.org/attachment.cgi?id=278245&action=edit
log results (bis)
The results of the previous patch.
--
You are receiving this mail because:
You are wat
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #9 from vice...@gmail.com ---
Created attachment 278243
--> https://bugzilla.kernel.org/attachment.cgi?id=278243&action=edit
add some log (bis)
Hi, added a few more printk for extra verbosity.
--
You are receiving this mail becaus
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #8 from vice...@gmail.com ---
Created attachment 278241
--> https://bugzilla.kernel.org/attachment.cgi?id=278241&action=edit
log results
Hi, here are the results asked for.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #7 from Chao Yu (c...@kernel.org) ---
Created attachment 278233
--> https://bugzilla.kernel.org/attachment.cgi?id=278233&action=edit
add some log
Can you apply this patch attached and reproduce this bug again?
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #6 from vice...@gmail.com ---
Hi, just found that the issue is also reproducible when mounted
with the "nodiscard" option, enabling TRIM via UDEV is enouth.
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #5 from vice...@gmail.com ---
Created attachment 278227
--> https://bugzilla.kernel.org/attachment.cgi?id=278227&action=edit
fsck.f2fs
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #4 from vice...@gmail.com ---
Hi! Yes, it is reproducible.
Each time TRIM is enabled via the UDEV rule and the FS mounted with
the discard option, the issue is triggered at the very first write attempt.
Before mounting fsck.f2fs was su
https://bugzilla.kernel.org/show_bug.cgi?id=200951
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #2 from vice...@gmail.com ---
Created attachment 278131
--> https://bugzilla.kernel.org/attachment.cgi?id=278131&action=edit
sg_vpd
--
You are receiving this mail because:
You are watching the assignee of the bug.
-
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #1 from vice...@gmail.com ---
Created attachment 278129
--> https://bugzilla.kernel.org/attachment.cgi?id=278129&action=edit
sg_readcap
--
You are receiving this mail because:
You are watching the assignee of the bug.
-
18 matches
Mail list logo
