Re: mkfs and mdadm support


Chronological Thread 
  • From: Scott Likens <scott@likens.us>
  • To: chef@lists.opscode.com
  • Subject: Re: mkfs and mdadm support
  • Date: Tue, 9 Jun 2009 10:22:57 -0700

well, if you are fortunate enough to have it already mounted you can do, with about any user

# mount
/dev/root on / type ext4 (rw,relatime,barrier=1,data="ordered)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
rc-svcdir on /lib64/rc/init.d type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1024k,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type tmpfs (rw,nosuid,relatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda6 on /home type ext4 (rw)
/dev/sda5 on /var/spool/imap type reiserfs (rw)
/dev/sda7 on /export type ext4 (rw)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)

Obviously won't work on things that are not mounted, but in a pinch this will get what you seek... as you see if it's mounted you know what filesystem it is and what options it's mounted with.

Scott

On Jun 9, 2009, at 10:18 AM, snacktime wrote:

That's kind of the conclusion I came to last night after thinking it over some more.  I've forked chef and started last night on the filesystem and raid resources.  Should be easy enough to re arrange if needed.

Would be nice if there was an available tool for detecting filesystem types.  Best I've found so far is parsing the output of parted.  Anyone know of a better way to handle this? 

Chris

On Tue, Jun 9, 2009 at 9:11 AM, Miguel Cabeça <cabeca@ist.utl.pt> wrote:
Hi,


So maybe there should be a top level filesystem resource that contain all of this.  Even after you add resources for mkfs, lvm, raid, etc.., you still need higher level logic to tie it all together, maybe a collection of definitions?

IMHO it would be too complicated to try to fit everything into the filesystem resource.

It would be simpler (famous last words) to have three resources like:
 filesystem
 raid
 volume

and combine them with definitions to achieve the complete goal (for example a xfs filesystem on top of an lvm2 volume, on top of a raid1 array)

Best Regards

Miguel Cabeça

!DSPAM:4a2e996b268771804284693!




Archive powered by MHonArc 2.6.16.

§