the filer server can started,but some files are missing.Please show me some advises.

[petty amonth]

A few days ago the filer server can't be started,so i change the dir-ids in the dir.log file.
But today i find some files that are normally downloaded before the problem happened are missing.
Please give me some advises and how to solve it!

[Chris Lu]

Depends on what you have manually changed in dir.log file. you can only pad some new lines for the missing directoth ids.

--
You received this message because you are subscribed to the Google Groups "Seaweed File System" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weed-file-syst...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[petty amonth]

Thanks for your reply!
I tried to add some new lines for the missing directory ids in the dir.log file.but when i started the filer server, the exact error info still exists.

the error info shows as follow:
F1114 15:26:21 58312 filer_server.go:25] Can not start filer in dir/weedfs/filer/: /S/37/49 should be have id 30547 instead of 30550!

the old lines before changing:
...
add     /S/20/C0  30530
add     /S/24/D7  30534
add     /S/04/90  30535
...
the new lines after changed
...
add     /S/20/C0  30530
add     /S/20/CR  30531
add     /S/20/CS  30532
add     /S/20/CT  30533
add     /S/24/D7  30534
add     /S/04/90  30535
...
the directory /S/20/CR,/S/20/CS and /S/20/CT don't existed actually.

If i changed the direcotry ids based on infomations from the errorlog files,the filer server can be started,but some files will not be downloaded from the filer server.

So Should i change something else in the dir.log files?

[Chris Lu]

These are on. What are the lines around 30547 and 30550?

On Nov 18, 2014 1:29 AM, "petty amonth" <amont...@gmail.com> wrote:

--

[petty amonth]

the lines around 30547 and 30550 are similar to the lines mentioned above.and i has added some lines ,but when started the filer server , the same error info happened.
the errorlog still shows:

[Chris Lu]

The lines you added between 30547 and 30550 are wrong.

--

[petty amonth]

when the problem just happened,the filer log showed:
filer_server.go:25] Can not start filer in dir/weedfs/filer/: /S/24/D7 should be have id 30531 instead of 30534!
then i tried two ways.
1: i manually add some lines mentioned above between the lines 30530 and 30534. but the filer server still can not be started and it has same error info.
2: i manually changed the direcotry ids based on the infomations from the errorlog. for example:
the  lines before changing:

...
add     /S/20/C0  30530
add     /S/24/D7  30534
add     /S/04/90  30535
...

the  lines after changed
...
add     /S/20/C0  30530
add     /S/24/D7  30531
add     /S/04/90  30532
...
the lines followed by the lines 30532 gradually increased untile the lines 30546. But starting the filer server still failed.
Then i tried to add some lines between the lines 30546 and 30550 as followed:

the old lines before changing:
...

add     /S/26/A1  30546
add     /S/37/49  30550
add     /S/11/83  30551
...
the  lines after changed
...

add     /S/26/A1  30546
add     /S/26/R1  30547
add     /S/26/S1  30548
add     /S/26/T1  30549
add     /S/37/49  30550
add     /S/11/83  30551
...
And the filer server still failed...

[Chris Lu]

I think the way to fix it is correct. Basically you do not change any existing lines, but only add some non-existing folders for the the missing directory ids. If it still fails, very likely it is failing on some other lines.

A side note is that there are too many folders created. The 3-level of folders are totally not necessary for weedfs. Just one level is enough. Adding other prefixes actually negatively impact the performance, although not a great impact.

Chris

--

[petty amonth]

Thanks a lot!
When viewing the changelist page of the wiki,I found that the weed of version 0.64 resolves directory log file error.So,Is the problem same as my problem? Please give me more infomations about the resolved directory log file error.
Now our implements of weed-fs use the 3-level of folders adapting to out programs and the folders will not be added or removed. In this case, if dont upgrade to new version ,the filer server can runs normally?

[Chris Lu]

Use the latest version. The fix is for this problem.

If no more directory changes, the filer would work fine. But upgrading is trivial.

Chris

--

[petty amonth]

Thanks!
When upgrading to new version, can i just replace the old weed executable with the new one? If  the new weed executable will read the old configurations and datas that are stored in the master server,volume server and filer server ? And if the files that are uploaded when using the old version of weed can be downloaded normally?
Or if i can just upgrade the filer server to the new version ,but the master server and volume server still use the old one?

[Chris Lu]

Just replace the binary. It's trivial. Only replacing filer server would also work.

Upgrading will prevent future problems. Still you would need to fix the dir.log file for current data.

Chris

--