Xsanity Sanity for Apple's Xsan and Final Cut Server.
  
Thursday, June 20 2013 @ 08:00 AM EDT
Topics
Storage (39)
People (1)
Xsan (105)
How To (26)
User Functions
Username:

Password:

Don't have an account yet? Sign up as a New User
Who's Online
Guest Users: 9
Sponsorship

Xsanity is proudly sponsored by:

Tekserve
The Old Reliable Mac Shop

XSAN Volume woes

 
Post new topic   Reply to topic    Xsanity Forums Forum Index -> Troubleshooting
View previous topic :: View next topic  
Author Message
mcgredo
JBOD
JBOD


Joined: 05 Sep 2006
Posts: 3

PostPosted: Tue Sep 05, 2006 4:14 pm    Post subject: XSAN Volume woes Reply with quote

So I upgraded to XSAN 1.4 (accidentally--hit the update software button without looking closely enough) and post-upgrade I'm having some problems. The volume Video tries to start, then I get these failures:

[0905 11:09:56] 0xa000ed98 (Info) File System Service 'Video[0]' now active on host '192.168.1.4:49466'.
[0905 11:09:56.979713] 0xa000ed98 (Debug) Node [1] [192.168.1.4:49470] connected.
[0905 11:09:56.983435] 0xa000ed98 (Debug) Node [2] [192.168.1.4:49469] connected.
[0905 11:09:56] 0x186d000 (Info) Node [1] [192.168.1.4:49470] Client Login (active 1).
[0905 11:09:56] 0x186e800 (**FATAL**) PANIC: /Library/Filesystems/Xsan/bin/fsm ASSERT failed "free_ip->i_idinode.idi_flags & InodeFlagFree" file inode.c, line 2302
.....lots of stuff....
[0905 11:09:56.995547] 0xa000ed98 (Debug) BRL SUMMARY [192.168.1.4] ReconDone cnt/1 avg/41 min/41 max/41.
[0905 11:09:56] 0x186e800 (**FATAL**) PANIC: aborting threads now.

Any idea what may be causing this?
Back to top
View user's profile Send private message
MattG
Xsan Master
Xsan Master


Joined: 15 Apr 2005
Posts: 456

PostPosted: Tue Sep 05, 2006 8:01 pm    Post subject: Inode issues.... Reply with quote

Looks like the volume is having inode issues...

Use Xsan admin to unmount the volume from all clients and then stop the volume.

Then, in Terminal, on the MDC, do the following commands, in order:

sudo cvfsck -vj <volname>
sudo cvfsck -vn <volname>
sudo cvfsck -v <volname>

where <volname> is the name of your volume. You will be asked to authenticate each time.

cvfsck will try to resolve the inode discrepancies, but be forwarned, you might have screwed the pooch with the wanton updates.

Which machine(s) did you do the update to?

Let this be a warning to all: unmount and stop the volume and use cvfsck to check the state of the volume before _any_ upgrades.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    Xsanity Forums Forum Index -> Troubleshooting All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Best Viewed on a Mac | Suggested Browser: Whatever floats yer boat.