Fedora Linux Support Community & Resources Center
  #1  
Old 2nd December 2011, 01:52 PM
Ridd1ck Offline
Registered User
 
Join Date: Nov 2011
Posts: 18
windows_7firefox
SSD Problem - Cannot Access lost+found

Hello,
I Have Fedora 15 64bit and in this server i run mysql cluster data nodes.
After Force shutdown of my server because of power lose of the data center,
i have no acces to lost+found folder.
What can i do now?

I use :
Code:
ls -lh
And the output is:
Code:
total 8.0K
drwxr-xr-x 2 root  root  4.0K Dec  2 03:03 backup
d????????? ? ?     ?        ?            ? lost+found
drwxr-xr-x 4 mysql mysql 4.0K Nov 30 14:32 mysql-cluster
And when i try:

Code:
cd lost+found
The output is

Code:
bash: cd: lost+found: Input/output error
The strange think is that this SSD have double size than the other SSD in the other same Server that i have who running the same things and have the same data.

When i try at the server with the problem:

Code:
df -h
The output is:
Code:
Filesystem            Size  Used Avail Use% Mounted on
rootfs                 66G  2.4G   60G   4% /
udev                   12G     0   12G   0% /dev
tmpfs                  12G     0   12G   0% /dev/shm
tmpfs                  12G  600K   12G   1% /run
/dev/sda1              66G  2.4G   60G   4% /
tmpfs                  12G     0   12G   0% /sys/fs/cgroup
tmpfs                  12G     0   12G   0% /media
/dev/sdb1             272G  103G  156G  40% /ssd
In the healthy server is

Code:
Filesystem            Size  Used Avail Use% Mounted on
rootfs                 66G  2.6G   60G   5% /
udev                   12G     0   12G   0% /dev
tmpfs                  12G     0   12G   0% /dev/shm
tmpfs                  12G  620K   12G   1% /run
/dev/sda1              66G  2.6G   60G   5% /
tmpfs                  12G     0   12G   0% /sys/fs/cgroup
tmpfs                  12G     0   12G   0% /media
/dev/sdb1             272G   54G  205G  21% /ssd


Can you help me with this?

Thanks.
Reply With Quote
  #2  
Old 2nd December 2011, 02:17 PM
jpollard Online
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,772
linuxfedorafirefox
Re: SSD Problem - Cannot Access lost+found

What filesystem is on the ssd?

This can make a significant difference as to how to approach the problem.

A journaled filesystem (ext3/4) then running fsck on the filesystem SHOULD correct the problem. An ext2 based system may have more problems, as you may need multiple passes.

If I remember right, the repair can re-create a lost+found directory.

In your case, it sounds like the lost+found directory itself got corrupted.

Normally, that shouldn't happen (unless it is a sign that the ssd itself is beginning to fail) as the lost+found directory is not referenced by anything while in normal use. This can happen if a power failure hit the device during an fsck run.
Reply With Quote
  #3  
Old 2nd December 2011, 03:38 PM
Ridd1ck Offline
Registered User
 
Join Date: Nov 2011
Posts: 18
windows_7firefox
Re: SSD Problem - Cannot Access lost+found

The file system is ext2.
This is very strange because after the power lose
The cluster cannot starts with some errors.
And when i use the --initial command for the cluster process (this recreates the filesystem of the cluster) didn't reduce the ssd size.

What can i do know?
Is difficult to me to try something because the cluster right at this time in ssd and is in productive mode.

Thanks.
Reply With Quote
  #4  
Old 2nd December 2011, 04:27 PM
jpollard Online
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,772
linuxfedorafirefox
Re: SSD Problem - Cannot Access lost+found

First, the filesystem has to be repaired.

The cluster very likely cannot start until it is fixed. It is also possible that other damage to the ssd has occurred, but until the filesystem is repaired there won't be much else that will work.

I'm actually surprised that the filesystem would even mount.

BTW, I hope you do have a backup of any needed files on the filesystem. The worst case recovery is to recreate the filesystem, which would leave it empty, but functional. Then restore any needed files.

What is the ssd providing to mysql? just cache? if so, then it should be able to be erased without damage to the database.

Last edited by jpollard; 2nd December 2011 at 04:31 PM.
Reply With Quote
  #5  
Old 2nd December 2011, 04:38 PM
PabloTwo Online
"Registered User" T-Shirt Winner
 
Join Date: Mar 2007
Location: Seville, FL
Posts: 6,054
linuxfirefox
Re: SSD Problem - Cannot Access lost+found

How about just trying,
Code:
chmod 0700 lost+found
Reply With Quote
  #6  
Old 2nd December 2011, 06:36 PM
jpollard Online
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,772
linuxfedorafirefox
Re: SSD Problem - Cannot Access lost+found

Its a corrupted filesystem - the modes are ? meaning that it couldn't be interpreted, and very likely cannot be written.

This usually happens when a block goes bad, but there are a few other situations that can cause it also (gvfs causes this for non-owners of the mountpoint).
Reply With Quote
  #7  
Old 2nd December 2011, 06:48 PM
PabloTwo Online
"Registered User" T-Shirt Winner
 
Join Date: Mar 2007
Location: Seville, FL
Posts: 6,054
linuxfirefox
Re: SSD Problem - Cannot Access lost+found

Quote:
Originally Posted by jpollard
Its a corrupted filesystem - the modes are ? meaning that it couldn't be interpreted, and very likely cannot be written.
That may very well be true. But then again, in the past on more than one occasion, I have had directories go all
Code:
d????????? ? ?     ?        ?            ?
on me and just resetting the permissions on those directories brought them back to normal, fully accessible and readable. This seems to happen when all exec bits are removed from the permissions on a directory.

Last edited by PabloTwo; 2nd December 2011 at 06:51 PM.
Reply With Quote
  #8  
Old 2nd December 2011, 09:17 PM
jpollard Online
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,772
linuxfedorafirefox
Re: SSD Problem - Cannot Access lost+found

Quote:
Originally Posted by PabloTwo View Post
That may very well be true. But then again, in the past on more than one occasion, I have had directories go all
Code:
d????????? ? ?     ?        ?            ?
on me and just resetting the permissions on those directories brought them back to normal, fully accessible and readable. This seems to happen when all exec bits are removed from the permissions on a directory.
No... all bits removed is a file/directory that looks like ---------, if the file is a directory then it is d---------.

Question marks occur only when the the stat system call returns with an I/O error.

The other cases are those of gvfs/fuse improper termination. The directory is hung, and an I/O operation fails due to the server process (gvfs/fuse) doesn't respond. After a timeout (and I don't know how long that is) then the file reverts. Sometimes this will happen when something refreshes the dcache entry (such as a chmod). But otherwise, an I/O error on an inode is not correctable. Especially one on disk.
Reply With Quote
  #9  
Old 2nd December 2011, 10:09 PM
stevea Offline
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,696
linuxfirefox
Re: SSD Problem - Cannot Access lost+found

you have a bad situation on your hands. The lost+found fs is there specifically to hold any lost inodes from a file-system error and it;s used by fsck.

So my advice in this special case:
1/ Unless you have a good backup - then make an image backup of the damaged partition before trying anything more including mounting that FS.
2/ DO NOT try to repair or remove the damaged lost&found - replace it.
I suggest (from the root directory of that FS).
Quote:
mv lost+found lost+forever
mklost+found
Then umount the fs and give it a fsck (which should use the NEW lost+found.

The 'mv' should just re-write the directory entry and likely NOT allocate any blocks. The mklost_+found will allocate space and may ruin the FS further - but frankly mounting the rw and mucking with DB could destroy what's left too.
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe

Last edited by stevea; 2nd December 2011 at 10:20 PM.
Reply With Quote
  #10  
Old 5th December 2011, 04:23 PM
Ridd1ck Offline
Registered User
 
Join Date: Nov 2011
Posts: 18
windows_7firefox
Re: SSD Problem - Cannot Access lost+found

Thanks guys for your help!
At this time the SSD is in a productive mode and this is very bad.
I try to stop the node and format the SSD and then i will start the node with initial.
At this time i don't have the possibility to try something because the data is critical for me.
Thanks
Reply With Quote
Reply

Tags
access, lost, problem, ssd

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
The lost&found folder glennzo Using Fedora 3 17th July 2011 01:00 PM
lost + found moosepig Linux Chat 3 21st August 2010 05:41 PM
Lost and Found... GreyCat Using Fedora 9 10th August 2008 08:58 AM
Tons of files in /lost+found lzapp Using Fedora 5 17th July 2007 08:19 PM


Current GMT-time: 23:55 (Wednesday, 23-07-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat