[SOLVED] - XFS filesystem problem after raid import

jly001 · 14. Januar 2014

Hi,

Originally coming from Arch linux, I installed OMV and re-used / imported the existing RAID 6 / XFS filesystem.
Now I found out I have a couple of directories showing as:

ls: cannot access 2013: Invalid argument
total 148
??????????? ? ? ? ? ? 2013

Directory is also not accessible...

Could this be due to a incompatibility between the Arch system and the OMV / debian system?
Or, is there something else going on?

Thx,
Johan.

raulfg3 · 14. Januar 2014

Zitat von "jly001"

I installed OMV and re-used / imported the existing RAID 6 / XFS filesystem.

in this case you have probably permission issues, so you need to recreate original users maintain his/her IDs or take control of this rebel folders.

jly001 · 14. Januar 2014

Mmm, I'm using the same username already, but in terms of ID's I have no clue what they were in my Arch system...
I have been trying different things already:

- 'check' raid6 via sync_action (I'm doing this once a week anyway via cron)
- 'repair' raid6 via sync_action
- xfs_check
- xfs_repair

Is there a way to be sure if this is a permission problem or a filesystem/raid problem ?

E.g. If it is a filesystem problem in the end, I do not want to 'zero' the XFS logs... because that would potentially make it worse, no?

Thx,
Johan

raulfg3 · 14. Januar 2014

Zitat von "jly001"

Is there a way to be sure if this is a permission problem or a filesystem/raid problem ?

yes.

open a shell and navigate from folders, go to parent folder of problematic and do a ls -s to see owner:group and rwxrwxrwx , once tested post it and check that are what you want.

jly001 · 15. Januar 2014

That is the problem actually.

owner:group and rwxrwxrwx show all as 'question marks'.

See output:

ls -ltr
ls: cannot access CLOUD: Invalid argument
ls: cannot access OneNote_Notebooks: Invalid argument
ls: cannot access PST: Invalid argument
ls: cannot access To Sort: Invalid argument
ls: cannot access VBox: Invalid argument
ls: cannot access aster: Invalid argument
ls: cannot access Desktop: Invalid argument
ls: cannot access My Apps: Invalid argument
total 2056
?????????? ? ? ? ? ? VBox
?????????? ? ? ? ? ? To Sort
?????????? ? ? ? ? ? PST
?????????? ? ? ? ? ? OneNote_Notebooks
?????????? ? ? ? ? ? My Apps
?????????? ? ? ? ? ? Desktop
?????????? ? ? ? ? ? CLOUD
?????????? ? ? ? ? ? aster
drwxr-xr-x 3 johan users 4096 Jan 9 2013 Documents

raulfg3 · 15. Januar 2014

this indicate that you have users that are not created in your new OMV, please take control of rebel folders and acomodate to your needs.

PD you need to login as root, and use command chown -r root:wheel /PATH-TO/VBox and chmod -r 775 /PATH-TO/VBox as example

once done do a ls -l /PATH-TO/VBox and the rest of problematic folders, and must show, if not, i'm totally out of ideas and perhaps is a problem, but do not know how to solve.

jly001 · 15. Januar 2014

# chown -R johan:users VBox
chown: cannot access `VBox': Invalid argument

# chmod -R 755 VBox
chmod: cannot access `VBox': Invalid argument

# stat VBox
stat: cannot stat `VBox': Invalid argument

Tried that already, but like you can see... No access...

jly001 · 15. Januar 2014

XFS_repair output...

No idea what to think about this... anyone?

Code

# xfs_repair /dev/md127
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - agno = 32
        - agno = 33
        - agno = 34
        - agno = 35
        - agno = 36
        - agno = 37
        - agno = 38
        - agno = 39
        - agno = 40
        - agno = 41
        - agno = 42
        - agno = 43
        - agno = 44
        - agno = 45
        - agno = 46
        - agno = 47
        - agno = 48
        - agno = 49
        - agno = 50
        - agno = 51
        - agno = 52
        - agno = 53
        - agno = 54
        - agno = 55
        - agno = 56
        - agno = 57
        - agno = 58
        - agno = 59
        - agno = 60
        - agno = 61
        - agno = 62
        - agno = 63
        - agno = 64
        - agno = 65
        - agno = 66
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - agno = 32
        - agno = 33
        - agno = 34
        - agno = 35
        - agno = 36
        - agno = 37
        - agno = 38
        - agno = 39
        - agno = 40
        - agno = 41
        - agno = 42
        - agno = 43
        - agno = 44
        - agno = 45
        - agno = 46
        - agno = 47
        - agno = 48
        - agno = 49
        - agno = 50
        - agno = 51
        - agno = 52
        - agno = 53
        - agno = 54
        - agno = 55
        - agno = 56
        - agno = 57
        - agno = 58
        - agno = 59
        - agno = 60
        - agno = 61
        - agno = 62
        - agno = 63
        - agno = 64
        - agno = 65
        - agno = 66
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Note - quota info will be regenerated on next quota mount.
done

Alles anzeigen

davidh2k · 15. Januar 2014

Judging from a quick google search it looks more like your filesystem is damaged. Hook up systemrescuedisk and try to access the files with its filerecovery tools.

Greetings
David

jly001 · 15. Januar 2014

After some more digging... And this webpage ==> http://www.doc.ic.ac.uk/~dcw/xfs_16tb/
I had some sort of an epiphany?

I remember the mount option -o inode64

mount -o inode64 /media/ecda24ee-ebf1-4e20-8e32-0eeee2f77346

And now all is back in working order !!

Remaining question: How do I make this permanent in OMV ? Can I just put it in my fstab? Or will it get overwritten?

davidh2k · 15. Januar 2014

You need to edit it to /etc/openmediavault/config.xml and put it there in the fstab section. Manual adds to the fstab will just be overwritten.

Greetings
David

raulfg3 · 15. Januar 2014

Please edit your first post and chage [HELP] by [SOLVED]

jly001 · 15. Januar 2014

Will the "edited" config.xml survive an openmediavault upgrade?
I'll set the topic to Solved once I have the answer to my last question about this issue

Thx for the help!
J.

ryecoaaron · 15. Januar 2014

Yes. OMV doesn't overwrite the config.xml file. It does overwrite config files for programs with settings from config.xml.

jly001 · 16. Januar 2014

Perfect!
Thx!

Marked topic as SOLVED

Jetzt mitmachen!