On 2024/3/25 14:56, Shinichiro Kawasaki wrote:
On Mar 25, 2024 / 11:06, Chao Yu wrote:
On 2024/3/25 10:14, Shinichiro Kawasaki wrote:
On Mar 24, 2024 / 20:13, Chao Yu wrote:
...
Hi Shinichiro,
Can you please check below diff? IIUC, for the case: f2fs_map_blocks()
returns zero blkaddr in
On Mar 25, 2024 / 11:06, Chao Yu wrote:
> On 2024/3/25 10:14, Shinichiro Kawasaki wrote:
> > On Mar 24, 2024 / 20:13, Chao Yu wrote:
> > ...
> > > Hi Shinichiro,
> > >
> > > Can you please check below diff? IIUC, for the case: f2fs_map_blocks()
> > > returns zero blkaddr in non-primary device,
On 2024/3/25 10:14, Shinichiro Kawasaki wrote:
On Mar 24, 2024 / 20:13, Chao Yu wrote:
...
Hi Shinichiro,
Can you please check below diff? IIUC, for the case: f2fs_map_blocks()
returns zero blkaddr in non-primary device, which is a verified valid
block address, we'd better to check m_flags &
On Mar 24, 2024 / 20:13, Chao Yu wrote:
...
> Hi Shinichiro,
>
> Can you please check below diff? IIUC, for the case: f2fs_map_blocks()
> returns zero blkaddr in non-primary device, which is a verified valid
> block address, we'd better to check m_flags & F2FS_MAP_MAPPED instead
> of map.m_pblk
On 2024/3/19 19:13, Shinichiro Kawasaki wrote:
On Mar 19, 2024 / 10:22, Chao Yu wrote:
On 2024/3/18 13:47, Shinichiro Kawasaki via Linux-f2fs-devel wrote:
I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
look in the commit, but it looks fine to me. So I thought the
On Mar 19, 2024 / 10:22, Chao Yu wrote:
> On 2024/3/18 13:47, Shinichiro Kawasaki via Linux-f2fs-devel wrote:
> > I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
> > look in the commit, but it looks fine to me. So I thought the cause is not
> > in the commit diff.
> >
On Mar 18, 2024 / 14:12, Daeho Jeong wrote:
> On Sun, Mar 17, 2024 at 10:49 PM Shinichiro Kawasaki via
> Linux-f2fs-devel wrote:
> >
> > I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
> > look in the commit, but it looks fine to me. So I thought the cause is not
> >
On 2024/3/18 13:47, Shinichiro Kawasaki via Linux-f2fs-devel wrote:
I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
look in the commit, but it looks fine to me. So I thought the cause is not
in the commit diff.
I found the WARN is printed when the f2fs is set up
On Sun, Mar 17, 2024 at 10:49 PM Shinichiro Kawasaki via
Linux-f2fs-devel wrote:
>
> I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
> look in the commit, but it looks fine to me. So I thought the cause is not
> in the commit diff.
>
> I found the WARN is printed when
I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
look in the commit, but it looks fine to me. So I thought the cause is not
in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices,
and read requests are mapped to the very first
On Mar 12, 2024 / 12:57, Yi Zhang wrote:
...
> Sorry, please use this one.
Thanks. I have succeeded to recreate the issue. Will take a look tomorrow.
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
On Mar 01, 2024 / 15:49, Yi Zhang wrote:
> On Wed, Feb 28, 2024 at 8:08 PM Yi Zhang wrote:
> >
> > On Wed, Feb 28, 2024 at 7:09 PM Shinichiro Kawasaki
> > wrote:
> > >
> > > On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> > > > Hello
> > > > I reproduced this issue on the latest linux-block/for-next,
On 2/29/24 23:49, Yi Zhang wrote:
Bisect shows it was introduced with the below commit:
commit dbf8e63f48af48f3f0a069fc971c9826312dbfc1
Author: Eunhee Rho
Date: Mon Aug 1 13:40:02 2022 +0900
f2fs: remove device type check for direct IO
(+Eunhee)
Thank you Yi for having bisected this
On Wed, Feb 28, 2024 at 7:09 PM Shinichiro Kawasaki
wrote:
>
> On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> > Hello
> > I reproduced this issue on the latest linux-block/for-next, please
> > help check it and let me know if you need more info/test, thanks.
>
> [...]
>
> > [ 4381.278858]
On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> Hello
> I reproduced this issue on the latest linux-block/for-next, please
> help check it and let me know if you need more info/test, thanks.
[...]
> [ 4381.278858] [ cut here ]
> [ 4381.283484] WARNING: CPU: 22 PID: 44011 at
Hello
I reproduced this issue on the latest linux-block/for-next, please
help check it and let me know if you need more info/test, thanks.
# ./check zbd/010
zbd/010 (test gap zone support with F2FS)[failed]
runtime... 3.752s
something found in dmesg:
[
16 matches
Mail list logo
