So the server looks fine besides the missing Shares. It's running a parity check now since it just shut off but all but one of my shares(which would be because of an auto package install) are missing. Odd?

 

Also, the share is not working.  When I ls /mnt/user/Movies it shows one folder but the Movies dir exist only on one disk(out of 5) and it has a lot more. If I ls /mnt/disk1/Movies I see the entire list.

Happened to me once after a power outage (got me a UPS soon afterwards).

 

REIFS is doing some checking and applying/rolling back of some journals and other stuff if I recall.

 

So until that completes, not all the mountpoints are available and SAMBA hasn't shared them yet.

 

I did a bunch of stuff thinking I was hosed and could have caused me issues.

 

Would recommend not messing with the shares until someone more knowledgable than I comments

The parity check was done so I rebooted and they came back. Weird.

The parity check was done so I rebooted and they came back. Weird.

Not weird at all.

 

When recovering from a power failure it is quite normal for the reiser file systems to replay transactions in their journals.  While this is happening, the attempt to mount the drives waits.  I've seen it take 15 minutes to replay the transactions on a busy 2TB drive. 

 

For those 15 minutes, any files/shares on that drive are not yet visible.

 

Problem is, the shared file system probably does not look for them to appear after the array has started.  So, you see those shares on disks that did mount quickly and you (apparently) need to stop and re-start the array for it to see those that are mounted after they took the time to replay the journal entries.

 

I'd send Tom @ lime-tech an e-mail and point him to this thread.  It might be something he can fix in a upcoming version.  (He can't change the behavior of the file-system, but he might be able to detect when they do mount and re-scan for additional user-shares.