From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan de Kruyf Subject: Re: [SPAM] Re: urgent help need! disk partition info lost Date: Fri, 6 Nov 2009 22:02:35 +0200 Message-ID: References: <856033f20911021106u771f823dkb48395958ad83a37@mail.gmail.com> <856033f20911041131n54c420fuf16b10fefb343188@mail.gmail.com> <856033f20911041719w12410864hdbdb8d5e6aed2070@mail.gmail.com> <856033f20911041957n7c88e5afvb60b6de9ee42bce7@mail.gmail.com> <856033f20911051002x79461f91o60e07f651a24f7c4@mail.gmail.com> <856033f20911060943i35d9cae4rcaf6a6dd12a6d845@mail.gmail.com> Reply-To: NILFS Users mailing list Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1216337607==" Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org Errors-To: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org To: NILFS Users mailing list --===============1216337607== Content-Type: multipart/alternative; boundary=001485e9a5a03b4f2b0477b95383 --001485e9a5a03b4f2b0477b95383 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oh du cleveres Kerlchen. What a way to spend a beautiful friday! Well you were smart after all I must say. And I would like to add that I have done similar things with ext2 and it was not half as easy. So Nilfs shines as far as I am concerned. And yes I did expect the partially lost file because the faulty superblock was written after the superblock at 0x400400. So let us sign a petition to the Master (Ryusuke are you listening!) to provide a special mount-flag for recovery purposes only so the mounting goes on as far as practical with suitable warnings. Perhaps you could supply a diff with the changes you made for your case Paul. > I guess you're going to make a backup every week from now :) Nah, he's got friends -- whaddo ye mean . . . . Regards, Jan de Kruyf. On Fri, Nov 6, 2009 at 9:24 PM, J=E9r=F4me Poulin w= rote: > On Fri, Nov 6, 2009 at 12:43 PM, Paul L wrote: > > Ok, based on the info so far, I've successfully recovered my files! > > > ... > > > > 6. Now it seemed no way to proceed, and I decided to try my luck by > > modifying nilfs_search_super_root(...) function to do a partial check > > instead of a full check (by changing the flag from 1 to 0). Compiled, > > installed, and rebooted. > > > This is where I'd like to add, the filesystem should always allow to > mount read-only whatever there is corruption or not, if there is bad > bad trouble it should mount read-only and ignore the cleanerd, isn't > that right? > > > It then all worked out from there. I immediately plugged in a USB > > drive, and copied all my files to the backup. Only one file seemed to > > have been damaged during the incident. I didn't bother to check if all > > the prevoius checkpoint on the nilfs2 partition worked and just went > > ahead and re-partitioned and re-formatted the SD card. > > > > I must thank Jan de Kruyf for the tremendeous help! Thank you all very > much! > > > > Now I'm just going to celebrate the magical recovery from the loss of > > months' hard work! > > > > > I guess you're going to make a backup every week from now :) > _______________________________________________ > users mailing list > users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org > https://www.nilfs.org/mailman/listinfo/users > --001485e9a5a03b4f2b0477b95383 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oh du cleveres Kerlchen. What a way to spend a beautiful friday!
Well yo= u were smart after all I must say. And I would like to add that
I have = done similar things with ext2 and it was not half as easy. So Nilfs shines<= br> as far as I am concerned.

And yes I did expect the partially lost fi= le because the faulty superblock was written after
the superblock at 0x= 400400.

So let us sign a petition to the Master (Ryusuke are you lis= tening!) to provide a special mount-flag
for recovery purposes only so the mounting goes on as far as practical with= suitable warnings.
Perhaps you could supply a diff with the changes you= made for your case Paul.

> I guess you're going to make a ba= ckup every week from now :)

Nah, he's got friends -- whaddo ye mean . . . .

Regards,
Jan de Kruyf.


On Fri, Nov 6, 200= 9 at 9:24 PM, J=E9r=F4me Poulin <jeromepoulin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On Fri, Nov 6, 2009 at 12:43 PM, Paul L <ninegua-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Ok, based on the info so far, I've successfully recovered my files= !
>
...
>
> 6. Now it seemed no way to proceed, and I decided to try my luck by > modifying nilfs_search_super_root(...) function to do a partial check<= br> > instead of a full check (by changing the flag from 1 to 0). Compiled,<= br> > installed, and rebooted.
>
This is where I'd like to add, the filesystem should always allow= to
mount read-only whatever there is corruption or not, if there is bad
bad trouble it should mount read-only and ignore the cleanerd, isn't that right?

> It then all worked out from there. I immediately plugged in a USB
> drive, and copied all my files to the backup. Only one file seemed to<= br> > have been damaged during the incident. I didn't bother to check if= all
> the prevoius checkpoint on the nilfs2 partition worked and just went > ahead and re-partitioned and re-formatted the SD card.
>
> I must thank Jan de Kruyf for the tremendeous help! Thank you all very= much!
>
> Now I'm just going to celebrate the magical recovery from the loss= of
> months' hard work!
>
>
I guess you're going to make a backup every week from now :)
_________________________________________= ______
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
= https://www.nilfs.org/mailman/listinfo/users

--001485e9a5a03b4f2b0477b95383-- --===============1216337607== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ users mailing list users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org https://www.nilfs.org/mailman/listinfo/users --===============1216337607==--