I don't know if this has been noticed before, but here goes.

 

When looking at the "Main" page, clicking on any of the drivers, shows you  the filesystem of the drive and the spin down period.

The file system is normally feiserfs. I installed a couple of new drives in my setup, both of which were previously formated with xfs.

After the unRaid system booted, the new drives were formated (by the unraid system) and were then ready to go.

However, if I clicked on the "diskx' link of one of the new drives, it would report that the drives were still formated as xfs.

 

After a system reboot, the filesystem shown was reiserfs.

 

So I guess everything works great behind the scenes, it's just that the reporting of the drive FS is based on the original FS on the drive at boot time, and it doesn't get updated afterwards.

 

Is this considered a bug?

I don't know if this has been noticed before, but here goes.

 

When looking at the "Main" page, clicking on any of the drivers, shows you  the filesystem of the drive and the spin down period.

The file system is normally feiserfs. I installed a couple of new drives in my setup, both of which were previously formated with xfs.

After the unRaid system booted, the new drives were formated (by the unraid system) and were then ready to go.

However, if I clicked on the "diskx' link of one of the new drives, it would report that the drives were still formated as xfs.

 

After a system reboot, the filesystem shown was reiserfs.

 

So I guess everything works great behind the scenes, it's just that the reporting of the drive FS is based on the original FS on the drive at boot time, and it doesn't get updated afterwards.

 

Is this considered a bug?

Sounds like a bug to me.  Not one that affects you too much, but it sounds as if the list is compiled when the server is first booted, but not updated when it creates the reiserfs on the disk.  Odds are very high it will show correctly when you reboot.

 

Good catch...

 

Joe L.