* [Bug] Inaccessible, unerasable file @ 2013-10-19 17:36 Max Muster 2013-10-22 11:09 ` Jaegeuk Kim 0 siblings, 1 reply; 6+ messages in thread From: Max Muster @ 2013-10-19 17:36 UTC (permalink / raw) To: linux-f2fs-devel There's a broken, ie. inaccessible and unerasable file on my f2fs partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0 32GB). ls reports: >cannot access shared.h: Input/output error >total 0 >-????????? ? ? ? ? ? shared.h The file has been on the partition for a couple of months already. I didn't report sooner as I could/can move its folder (but not the file itself) where it doesn't bug me and it doesn't appear to affect anything else. (I'm currently running Linux v3.12-rc5 with post-3.12 f2fs patches applied manually.) The partition is used primarily to store source code and as cache for ccache. I don't recall ever fiddling with this file directly; it probably happened during updating its repository or deleting just that. f2fs-tools's fsck (current git 2ad1fcd800) doesn't appear to do anything and aborts after some 30 seconds with: >Info: sector size = 512 >Info: total sectors = 42106880 (in 512bytes) >[fsck_chk_node_blk: 195] block addr [0xa40ae59] > >Assertion failed! >[fsck_chk_node_blk: 195] ni.blk_addr < F2FS_RAW_SUPER(sbi)->block_count If you would like me to post further info, please tell me which; I've got no idea how to further debug this. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug] Inaccessible, unerasable file 2013-10-19 17:36 [Bug] Inaccessible, unerasable file Max Muster @ 2013-10-22 11:09 ` Jaegeuk Kim 2013-10-22 20:50 ` Max Muster 0 siblings, 1 reply; 6+ messages in thread From: Jaegeuk Kim @ 2013-10-22 11:09 UTC (permalink / raw) To: Max Muster; +Cc: linux-f2fs-devel Hi, Thank you for the report. 2013-10-19 (토), 19:36 +0200, Max Muster: > There's a broken, ie. inaccessible and unerasable file on my f2fs > partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0 > 32GB). ls reports: > > >cannot access shared.h: Input/output error > >total 0 > >-????????? ? ? ? ? ? shared.h > > The file has been on the partition for a couple of months already. I > didn't report sooner as I could/can move its folder (but not the file > itself) where it doesn't bug me and it doesn't appear to affect anything > else. > > (I'm currently running Linux v3.12-rc5 with post-3.12 f2fs patches > applied manually.) > > The partition is used primarily to store source code and as cache for > ccache. I don't recall ever fiddling with this file directly; it > probably happened during updating its repository or deleting just that. > > f2fs-tools's fsck (current git 2ad1fcd800) doesn't appear to do anything > and aborts after some 30 seconds with: > > >Info: sector size = 512 > >Info: total sectors = 42106880 (in 512bytes) > >[fsck_chk_node_blk: 195] block addr [0xa40ae59] > > > >Assertion failed! > >[fsck_chk_node_blk: 195] ni.blk_addr < F2FS_RAW_SUPER(sbi)->block_count > > If you would like me to post further info, please tell me which; I've > got no idea how to further debug this. Um, I've never seen this kind of error so far. From the result of fsck, it seems that the inode of shared.h was lost. So, currently, there is no way to recover that inode and its data simply. It may need scan the whole partition to find the stale inode block. Two questions. - Have you experienced any sudden power-off before? - Can I test with the repository having the shared.h that you used? (I'd like to do a simple test storing that repository.) Thanks, -- Jaegeuk Kim Samsung ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug] Inaccessible, unerasable file 2013-10-22 11:09 ` Jaegeuk Kim @ 2013-10-22 20:50 ` Max Muster 2013-10-23 9:58 ` Jaegeuk Kim 0 siblings, 1 reply; 6+ messages in thread From: Max Muster @ 2013-10-22 20:50 UTC (permalink / raw) To: jaegeuk.kim; +Cc: linux-f2fs-devel Hi, I don't recall anything like a blackout, but since I like to run new software that's still in development, I have had a fair share of system crashes. As far as I'm aware this is the only file on the partition to ever become corrupted at the file system level, though. The repository was a simple (shallow) git clone of Google's gyp, available here: https://chromium.googlesource.com/external/gyp.git Such being the case, I have no need to restore the file, but being able to have it properly deleted would be nice. Yours tastky On 22.10.2013 13:09, Jaegeuk Kim wrote: > Hi, > > Thank you for the report. > > 2013-10-19 (토), 19:36 +0200, Max Muster: >> There's a broken, ie. inaccessible and unerasable file on my f2fs >> partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0 >> 32GB). ls reports: >> >> >cannot access shared.h: Input/output error >> >total 0 >> >-????????? ? ? ? ? ? shared.h >> >> The file has been on the partition for a couple of months already. I >> didn't report sooner as I could/can move its folder (but not the file >> itself) where it doesn't bug me and it doesn't appear to affect anything >> else. >> >> (I'm currently running Linux v3.12-rc5 with post-3.12 f2fs patches >> applied manually.) >> >> The partition is used primarily to store source code and as cache for >> ccache. I don't recall ever fiddling with this file directly; it >> probably happened during updating its repository or deleting just that. >> >> f2fs-tools's fsck (current git 2ad1fcd800) doesn't appear to do anything >> and aborts after some 30 seconds with: >> >> >Info: sector size = 512 >> >Info: total sectors = 42106880 (in 512bytes) >> >[fsck_chk_node_blk: 195] block addr [0xa40ae59] >> > >> >Assertion failed! >> >[fsck_chk_node_blk: 195] ni.blk_addr < F2FS_RAW_SUPER(sbi)->block_count >> >> If you would like me to post further info, please tell me which; I've >> got no idea how to further debug this. > > Um, I've never seen this kind of error so far. > From the result of fsck, it seems that the inode of shared.h was lost. > So, currently, there is no way to recover that inode and its data > simply. > It may need scan the whole partition to find the stale inode block. > > Two questions. > - Have you experienced any sudden power-off before? > - Can I test with the repository having the shared.h that you used? > (I'd like to do a simple test storing that repository.) > > Thanks, > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug] Inaccessible, unerasable file 2013-10-22 20:50 ` Max Muster @ 2013-10-23 9:58 ` Jaegeuk Kim 2013-11-19 15:34 ` tast ky 0 siblings, 1 reply; 6+ messages in thread From: Jaegeuk Kim @ 2013-10-23 9:58 UTC (permalink / raw) To: Max Muster; +Cc: linux-f2fs-devel Hi, 2013-10-22 (화), 22:50 +0200, Max Muster: > Hi, > > I don't recall anything like a blackout, but since I like to run new > software that's still in development, I have had a fair share of system > crashes. > > As far as I'm aware this is the only file on the partition to ever > become corrupted at the file system level, though. > > The repository was a simple (shallow) git clone of Google's gyp, > available here: > > https://chromium.googlesource.com/external/gyp.git > As I tested the above git, there was no functional problem on f2fs. So, could you give me the log of "fsck.f2fs -d 3"? It is the best you can give me the broken image though. Thanks, > Such being the case, I have no need to restore the file, but being able > to have it properly deleted would be nice. > > Yours > tastky > > On 22.10.2013 13:09, Jaegeuk Kim wrote: > > Hi, > > > > Thank you for the report. > > > > 2013-10-19 (토), 19:36 +0200, Max Muster: > >> There's a broken, ie. inaccessible and unerasable file on my f2fs > >> partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0 > >> 32GB). ls reports: > >> > >> >cannot access shared.h: Input/output error > >> >total 0 > >> >-????????? ? ? ? ? ? shared.h > >> > >> The file has been on the partition for a couple of months already. I > >> didn't report sooner as I could/can move its folder (but not the file > >> itself) where it doesn't bug me and it doesn't appear to affect anything > >> else. > >> > >> (I'm currently running Linux v3.12-rc5 with post-3.12 f2fs patches > >> applied manually.) > >> > >> The partition is used primarily to store source code and as cache for > >> ccache. I don't recall ever fiddling with this file directly; it > >> probably happened during updating its repository or deleting just that. > >> > >> f2fs-tools's fsck (current git 2ad1fcd800) doesn't appear to do anything > >> and aborts after some 30 seconds with: > >> > >> >Info: sector size = 512 > >> >Info: total sectors = 42106880 (in 512bytes) > >> >[fsck_chk_node_blk: 195] block addr [0xa40ae59] > >> > > >> >Assertion failed! > >> >[fsck_chk_node_blk: 195] ni.blk_addr < F2FS_RAW_SUPER(sbi)->block_count > >> > >> If you would like me to post further info, please tell me which; I've > >> got no idea how to further debug this. > > > > Um, I've never seen this kind of error so far. > > From the result of fsck, it seems that the inode of shared.h was lost. > > So, currently, there is no way to recover that inode and its data > > simply. > > It may need scan the whole partition to find the stale inode block. > > > > Two questions. > > - Have you experienced any sudden power-off before? > > - Can I test with the repository having the shared.h that you used? > > (I'd like to do a simple test storing that repository.) > > > > Thanks, > > -- Jaegeuk Kim Samsung ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug] Inaccessible, unerasable file 2013-10-23 9:58 ` Jaegeuk Kim @ 2013-11-19 15:34 ` tast ky 2013-11-20 19:52 ` tast ky 0 siblings, 1 reply; 6+ messages in thread From: tast ky @ 2013-11-19 15:34 UTC (permalink / raw) To: jaegeuk.kim; +Cc: linux-f2fs-devel Hello again, after buying a new USB stick and moving everything but the partition's broken file & folder to it, I am now able to send you an image after all. Although the 21 GB partition was supposed to only contain those two tiny entries, df still reported 1.8 GB as in use. I did "dd if=/dev/zero of=hugefile; sync; rm hugefile; sync" on it to boost the compression ratio, the file is at 406 MiB compressed. The image was taken with "dd if=/dev/sde2 bs=4096 conv=notrunc | xz -T8 -9 - > f2fs_bugged.xz". Please tell me if that was correct, especially since I intend to format the stick soon. As to the actual download link, I will send you that in a separate email as I am not fond of having potentially personal data open on the web. NB: fsck.f2f2 still fails with "[fsck_chk_node_blk: 198] ni.blk_addr < F2FS_RAW_SUPER(sbi)->block_count". On Wed, Oct 23, 2013 at 11:58 AM, Jaegeuk Kim <jaegeuk.kim@samsung.com> wrote: > Hi, > > 2013-10-22 (화), 22:50 +0200, Max Muster: >> Hi, >> >> I don't recall anything like a blackout, but since I like to run new >> software that's still in development, I have had a fair share of system >> crashes. >> >> As far as I'm aware this is the only file on the partition to ever >> become corrupted at the file system level, though. >> >> The repository was a simple (shallow) git clone of Google's gyp, >> available here: >> >> https://chromium.googlesource.com/external/gyp.git >> > > As I tested the above git, there was no functional problem on f2fs. > So, could you give me the log of "fsck.f2fs -d 3"? > It is the best you can give me the broken image though. > Thanks, > >> Such being the case, I have no need to restore the file, but being able >> to have it properly deleted would be nice. >> >> Yours >> tastky >> >> On 22.10.2013 13:09, Jaegeuk Kim wrote: >> > Hi, >> > >> > Thank you for the report. >> > >> > 2013-10-19 (토), 19:36 +0200, Max Muster: >> >> There's a broken, ie. inaccessible and unerasable file on my f2fs >> >> partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0 >> >> 32GB). ls reports: >> >> >> >> >cannot access shared.h: Input/output error >> >> >total 0 >> >> >-????????? ? ? ? ? ? shared.h >> >> >> >> The file has been on the partition for a couple of months already. I >> >> didn't report sooner as I could/can move its folder (but not the file >> >> itself) where it doesn't bug me and it doesn't appear to affect anything >> >> else. >> >> >> >> (I'm currently running Linux v3.12-rc5 with post-3.12 f2fs patches >> >> applied manually.) >> >> >> >> The partition is used primarily to store source code and as cache for >> >> ccache. I don't recall ever fiddling with this file directly; it >> >> probably happened during updating its repository or deleting just that. >> >> >> >> f2fs-tools's fsck (current git 2ad1fcd800) doesn't appear to do anything >> >> and aborts after some 30 seconds with: >> >> >> >> >Info: sector size = 512 >> >> >Info: total sectors = 42106880 (in 512bytes) >> >> >[fsck_chk_node_blk: 195] block addr [0xa40ae59] >> >> > >> >> >Assertion failed! >> >> >[fsck_chk_node_blk: 195] ni.blk_addr < F2FS_RAW_SUPER(sbi)->block_count >> >> >> >> If you would like me to post further info, please tell me which; I've >> >> got no idea how to further debug this. >> > >> > Um, I've never seen this kind of error so far. >> > From the result of fsck, it seems that the inode of shared.h was lost. >> > So, currently, there is no way to recover that inode and its data >> > simply. >> > It may need scan the whole partition to find the stale inode block. >> > >> > Two questions. >> > - Have you experienced any sudden power-off before? >> > - Can I test with the repository having the shared.h that you used? >> > (I'd like to do a simple test storing that repository.) >> > >> > Thanks, >> > > > -- > Jaegeuk Kim > Samsung > ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bug] Inaccessible, unerasable file 2013-11-19 15:34 ` tast ky @ 2013-11-20 19:52 ` tast ky 0 siblings, 0 replies; 6+ messages in thread From: tast ky @ 2013-11-20 19:52 UTC (permalink / raw) Cc: linux-f2fs-devel If there are no further questions, I will format the stick this weekend. On Tue, Nov 19, 2013 at 4:34 PM, tast ky <tastky@gmail.com> wrote: > Hello again, > > after buying a new USB stick and moving everything but the partition's > broken file & folder to it, I am now able to send you an image after > all. > > Although the 21 GB partition was supposed to only contain those two > tiny entries, df still reported 1.8 GB as in use. > > I did "dd if=/dev/zero of=hugefile; sync; rm hugefile; sync" on it to > boost the compression ratio, the file is at 406 MiB compressed. > > The image was taken with "dd if=/dev/sde2 bs=4096 conv=notrunc | xz > -T8 -9 - > f2fs_bugged.xz". Please tell me if that was correct, > especially since I intend to format the stick soon. > > As to the actual download link, I will send you that in a separate > email as I am not fond of having potentially personal data open on the > web. > > NB: fsck.f2f2 still fails with "[fsck_chk_node_blk: 198] ni.blk_addr < > F2FS_RAW_SUPER(sbi)->block_count". ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-11-20 19:52 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-10-19 17:36 [Bug] Inaccessible, unerasable file Max Muster 2013-10-22 11:09 ` Jaegeuk Kim 2013-10-22 20:50 ` Max Muster 2013-10-23 9:58 ` Jaegeuk Kim 2013-11-19 15:34 ` tast ky 2013-11-20 19:52 ` tast ky
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).