On 2024/9/23 23:14, Jaegeuk Kim wrote:
On 09/23, Chao Yu wrote:
On 2024/9/20 23:38, Daeho Jeong wrote:
On Thu, Sep 19, 2024 at 6:14 AM Chao Yu wrote:
On 2024/9/14 5:28, Daeho Jeong wrote:
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the
On 09/23, Chao Yu wrote:
> On 2024/9/20 23:38, Daeho Jeong wrote:
> > On Thu, Sep 19, 2024 at 6:14 AM Chao Yu wrote:
> > >
> > > On 2024/9/14 5:28, Daeho Jeong wrote:
> > > > From: Daeho Jeong
> > > >
> > > > F2FS should understand how the device aliasing file works and support
> > > > deleting
On 2024/9/20 23:38, Daeho Jeong wrote:
On Thu, Sep 19, 2024 at 6:14 AM Chao Yu wrote:
On 2024/9/14 5:28, Daeho Jeong wrote:
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the file after use. A device aliasing file can be created by
mkfs.f2fs
On Thu, Sep 19, 2024 at 6:14 AM Chao Yu wrote:
>
> On 2024/9/14 5:28, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > F2FS should understand how the device aliasing file works and support
> > deleting the file after use. A device aliasing file can be created by
> > mkfs.f2fs tool and it can map
On 2024/9/14 5:28, Daeho Jeong wrote:
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the file after use. A device aliasing file can be created by
mkfs.f2fs tool and it can map the whole device with an extrent, not
using node blocks. The file spa
From: Daeho Jeong
F2FS should understand how the device aliasing file works and support
deleting the file after use. A device aliasing file can be created by
mkfs.f2fs tool and it can map the whole device with an extrent, not
using node blocks. The file space should be pinned and normally used fo
