Ext2 redux

https://bugs.archlinux.org/task/31568
"The ext4 supports ext2/ext3 FS so no need to activate the old modules."
Yes. So why won't Arch mount ext2 without help? Legacy fstab files across the universe say 'ext2' or 'auto' - so for end users, Arch just breaks.
mount -t ext2 ... should work
mount -t auto ... should work for ext2 like everything else
ext2 in fstab should work
What happens instead: Arch reports it doesn't know any such thing as an ext2 filesystem.
Me, I don't care how ext2 support is accomplished, but Arch should supply it, not end users. Unless a sysadmin hip to obscure ext4 capability details is on call, then what an end user sees is a very standard Linux fs which won't mount, so Arch seems crudware.
Make Arch use ext4 for ext2 fs behind the scenes. Don't bomb over an ACCURATE fstab that says ext2. Right now, Arch reports ext2 as an unknown filesystem.
Needless breakage gives Arch a false public image of instability. Old ext2 is too important to write off. By the way, even Tso himself wishes to dump ext4 for btrfs. Today's "cool" is tomorrow's "has been." And ext2 doesn't the carry patent problems of FAT, which can affect its appearance in commercial settings. Biz people care little about fs quality, but much about time to market, embedded memory constraints, and breadth of os / tool support. We'd all like to see FAT disappear, but it's running on half the devices in your home, I wager. And hilariously enough, FAT is the single most cross-platform capable fs between the 3 big OS platforms (Mac/Win/Linux). Such is life. Of all the non-MS, Linux filesystems, the one with the most Win/Mac support is ext2.
P.S. I hope the netiquette is ok? It seemed more reasonable to post than reopen a ticket. The bug board needs some way to folloup closed items. Anyway, thanks to all for giving a hearing. I still of course consider Arch the best *nix distro bar none. Just trying to help the cause here!

(jasonwryan, calm. Netiquette meant whether to reopen, not speak. Arch is touchy even flattered. If I scored unsettling points, well, ahem....I've sysadminned for donkey's years. The ticket desk won't allow followups and I was trying to be good by not reopening.)
To those who asked,
Linux <hostname> 3.5.3-1-ARCH #1 SMP PREEMPT <timedate> x86_64 GNU/Linux
failed on a udev hotswapped ext2 USB drive
mount -t ext2 ...
with message that ext2 is an unknown filesystem.
The same ext2 booted another box fine. I wasn't saying everything about ext2 is broken, but that Arch should never report ext2 as unknown filesystem. Both 'ext2' and 'auto' tags should 'just work' in all possible usages (fstab, manual console mount, DE auto-mount, whatever).
If I have some weird config causing a message others don't see (very possible, I just didn't think of it that way after ticket closure), then I would like to learn what. The sys is well maintained and standard. Stock Arch kernels all the way. If Arch devs never intended such a message to appear, then I may have found a bug and need to file a report. It may need some backtrack, as I already reformatted to UN-journaled ext4 just to use the device with Arch boxes.
Thanks all!

Similar Messages

Intermittent Shut Down Syndrome Redux 2

The old redux thread was locked, probably because it became too large. This is an updated redux to replace the old one.
MacBook Intermittent Shut Down
Redux 2 (Updated Oct 13, 2006)
Guy Kuo
Do a google search for "macbook random shutdown" and you will find many people with similar problems reporting on various forums. Most frequently, the MacBook operates normally for several weeks or months, but mysteriously begins intermittently shutting off suddenly. The shutdowns are not accompanied by kernel panics, but instead the machine simply goes black and the machine is off. Initially, the cause of this problem was not known and early repairs of the main logic board and heat sink did not incorporate the changes made after the cause of the problem was discovered. Numerous attempts at user, ad hoc, solutions have been posted, but the only definitive and permanent solution requires repair by Apple.
The problem as difficult to characterize because its symptoms mimic more common causes of system failure (bad RAM, improperly seated RAM, improperly seated hard drive, bad software install, bad battery, bad AC adapter, corrupted PRAM, corrupted NVRAM) which ALL must be ruled out before making the sudden shutdown diagnosis. The problem's intermittent nature means it may not be possible to reproduce on demand.
At present, this problem is being addressed by Apple and affects at least serial number range 4H617-4H635. MacBooks produced after that date should have an updated heat sink assembly which does not have that problem. The problem seems to have two root causes.
1. Two heat sensor wires in contact with the heat sink can melt and once that occurs, intermittent shorting of the wires causes the machine to sense an emergent temperature problem and the system performs an immediate power down.
2. Also, as described in a MacTalk Australia posting ..... 2 small connectors that bake under the enclosed heat on the Macbook (the Mac book Pro has more space and 2 fans) these connects then loose contact with their pins.... Once contact is lost, the machine does an emergency power down
The common thread is that heat in the original heat sink and thermal sensor design eventually may cause the problem to occur. Once contact or insulation problems begin, the machine can begin suddenly shutting down while cold or hot. Until sufficient heat is built up, the MacBook operates without any issues. It is possible for an early MacBook to operate normally for months before heat causes the problem to occur. Indeed it is possible a machine may never exhibit this problem despite having this weakness in its components. None the less, the early MacBooks have a heat sink and thermal sensor wiring harness that is inherently prone to deterioration. Because the risk of deterioration increases over time, it is reasonable to expect more early MacBooks to develop intermittent shutdown problems as time passes.
There are some early reports that even a heat sink assembly replacement repair does not always solve the issue. In such cases, a logic board replacement may also be necessary, but at this point, heat sink assembly replacement should solve the identified problem unless the MLB was also somehow damaged.
The current count of affected MacBooks has not been disclosed, but well over 1,000 machines have been reported on-line independent of Apple. The actual number of early MacBooks which will eventually be affected may be significantly larger even if one discounts the tendency of the web to amplify negative news.
Because heat is the root cause of the problem, two camps have appeared regarding how to deal with this issue. This author believes that the MacBooks should be allowed to warm to full operating temperature by running some high CPU usage tasks (with normal circulation around the case) for several hours and then seeing over the next few days if the problem occurs. The rationale is reveal any tendency for the problem while the MacBook is within warranty and before any critical usage. The other camp believes that the MacBook should only be used lightly and never allowed to get warm enough to induces the problem. The reader is left to choose their own course.
Only a fraction of shutdowns are due to this particular fault. A large number of other reasons must be ruled out before a MacBook owner should become convinced their machine is one which suffers this problem. Bad RAM, poorly seated RAM, improperly installed hard drive, corrupted OS, corrupted plists, bad batteries, bad chargers, corrupted PMU, and corrupted NVRAM all need to be ruled out first. During your call to Apple care you may be asked to perform checks to rule out the above list. Once a diagnosis of intermittent shut down is made, repair can take days to weeks depending on availability of parts and whether additional components beyond the heat sink assembly needs to be repaired. Once repaired, the MacBook is less likely to redevelop the problem, but as of this date, long term usage of several months has not had time to happen.
It is the hope of this writer that Apple will continue to assist its customers with this hardware "defect." So many first time Apple owners could be lost forever if this is not addressed openly and aggressively.

Are you sure RSD is the problem? Then, first, be sure you have downloaded all the updates. The smc update (late October) stopped RSD for many people. If you're updated, then you may need a new heatsink. That's what stopped it for me. I had it replaced at an authorized repair center while I waited - only took a couple of hours. You are still under warranty, so repair will be free if RSD is indeed the problem. You can look on these apple pages for the nearest Apple Store or authorized repair center.
In the meantime, I found it very helpful to hold down the on button for 5 seconds when I restarted the macbook. That kept the processor speed down to 1.0 gH, and for some reason, for me and for some other users, RSD never happened while in that mode.
Let us know how it goes!

[solved] How to convert fs from ext2 to ext3 on root partition?

Hello there!
Edit: It seems that the plan works! apparently it worked for alleyoopster also on a mounted fs.
As the title says, I want to convert my fs on / from ext2 to ext3. After some research I think I know what
to do, but want to make sure that I don't mess anything up....
So here is the plan:
boot with an install disc and leave the root partition unmounted (I know that in theory the conversion should
work on a mounted fs, but it feels awkward to me and I want to avoid it....).
Then use the
tune2fs -j /dev/xxx
command (the defaults for the forced checks are ok with me). Then reboot with the CD still in place, but use
this time root=/dev/xxx. Then I can change my /etc/fstab (ext3 should have been able to be mounted as ext2 at
the moment). Finally I have to rebuild my initrd image with
mkinitcpio -p kernel26
Then I should be able to boot into my system. And now the question: Can anyone verify that this is a valid approach
and will work? Or knows a better way to do it?
I'm grateful for any input
Last edited by alafanky (2007-11-26 15:41:35)

Have a look at the man for tune2fs and mkinitcpio
man tune2fs
man mkinitcpio
I am looking at doing the same and as far as I can figure out it goes like this, BUT this is not a proven method just what I am thinking of doing, Maybe someone else can correct or add to this or confirm that it will work.
1. Add journal parameter like this:
tune2fs -j /dev/sda1
2. Change the partition type from ext2 to ext3 in /etc/fstab
3. For a standard kernel re-create ramdisk with preset parameters (no good for custom kernel)
mkinitcpio -p kernel26
As the system is mounted it will create the journal inode in the top level, don't delete this, it will get hidden into the filesystem on reboot.
Let me know if you make some progress. I may get brave and try it later.
So in answer, yes pretty much the same but I think you can do it with the fs mounted.
Last edited by alleyoopster (2007-11-26 12:44:29)

How to read contents of the Super Block ext2

there I'm working on traversing an ext2 filesystem to read from it and I'm stumped at the first hurdle. The filesystem has a block size of 1024 bytes, so I need to read from the first 1024 bytes into an array to get Block Group 0. From there I need to go to the position of the super block, but I don't know how to go through the following first steps:
1 Find the Group Descriptor 2 Read the Inode Table Pointer value to find the block containing the first inode 3 Read Inode 2 (the root directory/ top of the filesystem) -- the length of each inode is given in the Group Descriptor 4 Traverse the filesystem as shown above to locate the file and its contents/ data blocks
I have some code below that reads the file in one go.
try { aFile = new RandomAccessFile("ext2fs", "r"); FileChannel fileChannel = aFile.getChannel(); long fsize = fileChannel.size(); ByteBuffer buff=ByteBuffer.allocate(1024); fileChannel.read(buff,1024L); buff.flip(); byte[] data = buff.array(); System.out.format("%s\n", new String(data)); buff.clear(); fileChannel.close(); aFile.close(); } catch (IOException e) { System.out.println("File not found"); } here
Thanks

The best solution is that you redesign your program so that it does not depend on the order of the entries in the properties file.
If you really want to stay with your design, you will have to read the properties file yourself, line by line, just like you would read any other text file, and parse the content of each line yourself.
BufferedReader in = new BufferedReader(new FileReader("stuff.properties"));
String line;
while ((line = in.readLine()) != null) {
// Parse the line, use e.g. String.split() to split it around the '='
in.close();

EXT2 or EXT3 on Linux for 10g?

Would EXT2 file system (Linux) be more appropriate for 10G datafiles since journal is essentially done by Oracle itself through redo logs and archived logs?
What's your experience with different file systems?
Same question for flash recovery area?

Hi mishomor
I would advice you to use ext3 as it has journalizing.
Read also that :
Doc ID: Note:236679.1
Subject: Comparing Performance Between RAW IO vs OCFS vs EXT 2/3
What about using raw devices.
read that
http://download.oracle.com/docs/cd/B19306_01/install.102/b15667/pre_install.htm#CIHHFGBA
Regards,
Hub
Edited by: Hub on Nov 14, 2008 9:04 PM
Edited by: Hub on Nov 14, 2008 9:06 PM

Determine filesystem type - EXT2, FAT32, NTFS, or other

Is it possible to determine file system type (EXT2, EXT3, FAT32, NTFS or other types) of the host media hard drive/USB key in Java?
Best Regards,
Karthigan.

[email protected] wrote:
I wrote a back up application. It works great if I am backing up data from NTFS to NTFS or FAT32 or FAT32 - basically across same filesystem types. If I run the same backup application from NTFS to FAT32 media, files that need not be copied over get copied over unnecessarily - because the timestamp accuracy/format of NTFS is different from FAT32. It just is not very appealing if files get copied over for no reason due to timestamp variation across filesystems. I was hoping to see if there was a way around it. The trick in this case might be to create a file on the target volume, set its last-changed date to a certain value, then read back its last-changed date and see whether you get back what you consider to be a date lacking in accuracy. Then instead of comparing an accurate date to an inaccurate date, and doing unnecessary work, you could apply some kind of algorithm to the accurate date to apply the inaccuracy before comparing the two dates. Or something like that.

An ext2 partition problem on install & multiple swap

I'm installing Arch on a second machine. This one has 2 scsi drives. I set up a /boot partition at /disc0/part1, had it formatted as ext2. I put a swap partition on this drive. This is marked bootable. The rest of the partitions are reiserfs.
I installed grub into /disc0/disc, which I understand is the MBR.
When the machine reboots after installation, I get an error:
fsck.ext2: No such file or directory while trying to open /dev/discs/disc0/part1
/dev/discs/disc0/part1: The superblock could not be read or does not describe a correct ext2 filesystem.
It goes on to suggest running e2fsck.
Since I originally posted this I ran knoppix on the machine, checking with Qtparted shows that the partition is fine, all the files that should be there are there.
1. What am I doing wrong? I know I don't technically need a /boot partition, and if it comes to that, I'll do without, but don't understand why that would be the problem.
2. I've read that performance is better if you have a swap on each drive if more than one. How do I create the second swap? I've created a partition for it, but don't know how to mark it as swap.

Ok, let me elaborate:
From the error messages you get it seems that grub successfully boots the kernel but the kernel fails to find your filesystem/swap partitions. This can have several reasons but the non-existence of the appropriate device nodes in /dev seems to be the problem in your case.
In your /etc/fstab the filesystem and swap entries are probably configured using devfs-style names, because that is what the Arch installer does set up.
E.g. /dev/discs/disc0/part1 for /boot and
/dev/discs/disc0/part2 for /
etc. ymmv
Now the point is that these entries do NOT exist by default, devfs or udev have to create them, usually they are symlinks to traditional entries like /dev/hda1 or /dev/hda2 (or the other way round, in case of devfs).
Now, if you are using neither devfs nor udev you won't have the proper devfs-style device entries in your /dev directory and that's causing to kernel to hickup because he simply cannot find the discs you tell him to mount. Normally you configure grub/lilo to tell the kernel which partition he shall use as / (thats the root=/dev/whatever option for the kernel)
Therefore you MUST run either one of devfs or udev to see the proper device entries. If you are using neither then you will have to adapt your /etc/fstab and /boot/grub/menu.lst or the kernel won't be able to mount the filesystems nor be able to activate the swap partitions.
As Arch Linux 0.7 does NOT install udev by default you will either have to use devfs (this is done by NOT using the devfs=nomount option) or install udev (then you'll probably want to set the devfs=nomount option).
Cheers,
Dominik

ITunes 7 not working with MyTunes Redux

I use mytunes redux to copy my music to different household computers, but after downloading itunes 7, all of a sudden it doesn't work. After a download is complete, an error message popos up saying something about an "unregistered library"
is there a compatability issue here or do I need to update some preferences or what?

mytunes redux is not made or recomended by Apple, you may want to contact the maker of that application to see if they have an update their software.
This article describes different methods for moving purchased music between authorized computers:
http://docs.info.apple.com/article.html?artnum=93366

[SOLVED] mount: unknown filesystem type 'ext2'

I probably have the most complicated first-time arch setup that you'll ever hear a n00b post. XD
I just finished setting up an encrypted arch box with a usb boot drive (it contains the key-file), but when I go to boot, the system reports the following:
mount: unknown filesystem type 'ext2'
Of all the things to break! Ext2???!
This is for the default boot mode, when boot into the fallback initramfs mode, the arch box boots up fine (although it takes 2 whole minutes). I think that the issue is that I'm missing a module in my mkinitcpio.conf file.
/etc/fstab file:
UUID=1245ASDF / btrfs discard,autodefrag,compress=lzo,rw,relatime,ssd,space_cache 0 0
UUID=2245ASDF /boot ext2 rw,noatime 0 2
UUID=3245ASDF none swap defaults 0 0
/etc/mkinitcpio.conf file:
HOOKS="base btrfs udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
/etc/default/grub file:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda:enc cryptkey=/dev/sdb2:ext2:/keyfile crypto=sha512:twofish-xts-plain64:512:0:"
Last edited by a-jamesregan (2015-04-13 19:15:48)

Wow, there was literally a note about the exact issue I was having on the wiki...
https://wiki.archlinux.org/index.php/Mkinitcpio#MODULES
Note: If using reiser4, it must be added to the modules list. Additionally, if you will be needing any file system during the boot process that is not live when you run mkinitcpio — for example, if your LUKS encryption key file is on an ext2 file system but no ext2 file systems are mounted when you run mkinitcpio — that file system module must also be added to the MODULES list. See Dm-crypt/System configuration#cryptkey for more details.
PS: How do I mark an issue as solved?
Last edited by a-jamesregan (2015-04-13 10:28:20)

[Autosolved] "EXT2-fs: Magic mismatch, very weird !"

I've just bought a SD (2 GB) and i would like to format it to ext2.
I've followed this path:
# mke2fs /dev/sdc1
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
124416 inodes, 495920 blocks
24796 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=511705088
16 block groups
32768 blocks per group, 32768 fragments per group
7776 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mount /dev/sdc1 /mnt/ipod1
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
usb 6-4.1: new full speed USB device using ehci_hcd and address 73
usb 6-4.1: configuration #1 chosen from 1 choice
scsi40 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 73
usb-storage: waiting for device to settle before scanning
scsi scan: INQUIRY result too short (5), using 36
scsi 40:0:0:0: Direct-Access OEI-USB MMC/SD 2.01 PQ: 0 ANSI: 0
sd 40:0:0:0: [sdc] 1985024 1024-byte hardware sectors (2033 MB)
sd 40:0:0:0: [sdc] Write Protect is off
sd 40:0:0:0: [sdc] Mode Sense: 0b 00 00 08
sd 40:0:0:0: [sdc] Assuming drive cache: write through
sd 40:0:0:0: [sdc] 1985024 1024-byte hardware sectors (2033 MB)
sd 40:0:0:0: [sdc] Write Protect is off
sd 40:0:0:0: [sdc] Mode Sense: 0b 00 00 08
sd 40:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 40:0:0:0: [sdc] Attached SCSI removable disk
sd 40:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
EXT2-fs: Magic mismatch, very weird !
Has Anyone Seen this?
UPDATE: My Card Reader has died So, this error, is imputable to an hardware malfunction
Last edited by Cagnulein (2008-04-28 10:54:21)

After some time I recognized that I went into the wrong direction before. I got, that my real problem is not libatasmart, but the module sr_mod which is timing out and causing ksoftirqd to run with 100% cpu-usage of one processor thread (which is very nice, because otherwise the kernel would crash because of all the soft interrupts). So I went on and removed sr_mod temporarily.
rmmod sr_mod
This works pretty well for me since I can suspend now as much as I want and the system wakes up after all. I still get this small message:
ata1: ACPI set timing mode failed (status=0x300b)
after resume, but this seems not to be a bigger problem.
The more interesting thing is, that you can not mount CDs or DVDs if you remove sr_mod from the kernel, because that is what I think it is made for. As I still like to use this type of media, it is pretty annoying, that I can't
modprobe sr_mod
after a resume, because than I get a lot of small soft interrupts and sr_mod is timing out again.
Btw: I use a laptop with a SIS 966 chipset. Might that cause all the trouble? Can anyone think of any further reading or trying or bugreporting?

Converting btrfs back to ext2/3/4

If you convert a ext2/3/4 to btrfs with btrfs-convert you get a snapshot/subvolume containing your ext2 fs. An Image.
If you delete this image you cant use btrfs-convert -r to roll-back to ext2/3/4
now my question.
Is there any way to create this image with an existing btrfs? So to roll-back to extX without an exisiting image of it.

i could just tar my Home Directory and do a new install. I just dont have a place for my HOME Folder...
maybe someone is willing to write a converter
Last edited by Vamp898 (2010-08-30 06:18:15)

Any benefits to using Ext4 over Ext2 on SSD, or USB flash drive?

Hi.
I've been using Linux on, and off, again for about two years now, and I never really bothered using anything outside of the extn file systems.
I had at one point only used ext2 only on usb installs, and usually on temporary installs of RIPLinux, Parted Magic, or Puppy Linux.
But... now we have the option to disable journaling with tune2fs, or at the very least mounting the partition with options 'noatime', 'barrier=0', or 'nobh', should we use ext4 for any of these devices?
Are there any ext4 improvements over ext2/3 that would actually apply to SSDs, or other flash devices?
Right now I'm currently running Arch from an USB. It's being used to stream media to a video game console, download files in the 200 - 500 MB range, and act as my media viewer for movie files. ie - mpeg, mp4, mkv, and flv. My original idea was to have a future proof system setup that I could eventually clone over to my replacement hard-drive when it comes in the mail.
Should I just make the switch back to ext2, or does ext4 have benefits over ext2 on these types of devices?
While I'm considering a persistent journal disable, my only Arch partition is mounted as follows in the fstab.
UUID=546043fd-170f-4ed4-8af0-136113627e8c / ext4 defaults,noatime,barrier=0 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/tmp tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/lock tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/run tmpfs defaults,noatime,mode=755 0 0
tmpfs /var/cache/pacman/pkg tmpfs defaults,noatime 0 0
tmpfs /var/abs/local/yaourtbuild tmpfs defaults,noatime 0 0

midenok,
Welcome to Arch Linux. Take note that this is an old thread (but not overly so). When reviving old threads, we generally encourage creating a new thread and linking to the old. In this case, your answer is pertinent to the thread, and that thread had not reached a logical conclusion, so you are fine. I just wanted to drop this note so others know that a moderator has seen it.
Again, welcome.

[Solved] Grub after moving from ext2 to ext4

When I boot without a live cd I am staring at the grub1 rescue console. I followed the instructions here to go from ext2 to ext 4 http://www.ghacks.net/2010/08/11/convert-ext23-to-ext4/
When I got to the part about changing /etc/fstab from ext2 to ext4, I noticed my /etc/fstab was empty. I suppose that's what I get for meddling with something I don't completely understand but I've consistently followed instructions on the wiki and done fine with plenty of other things I didn't understand.
Since this epic disaster I've managed to Chroot in and change my /etc/fstab to depict ext4 and mkinitcpio -p linux and change my /etc/default/grub to direct rootfstype=ext4 and run grub-mkconfig -o /boot/grub/grub.cfg.
I feel like this is salvagable but I am at a complete loss as to where to go from here. My hd layout is as follows, my boot is recognized as a ext4 fs, everything seems to be intact I just cannot boot. One thing I did notice that is out of place is that the grub console I am booting to is grub-legacy. I am uncertain as to why because I was using grub2. I suspect it was due to me using fsarchiver to backup my ext2 boot and then reinsert it onto an ext4 fs or because I am using the arch install disk and the grub-install command put grub1 on it.
/dev/sda1 /boot ext4
/dev/sda2 swap
/dev/sda3 / btrfs
/dev/sda4 /home btrfs
I am guessing what probably has to happen is I need to reinstall grub2 onto /dev/sda1 . Would it be as easy as pacman -S grub2-bios while in chroot?
Last edited by jallenusn (2012-07-09 21:22:52)

I am going down the steps to reinstall grub2 now. I ran blkid -c /dev/null and it returned this. the UUID's are actually filled in on what it returns. I left them blank for obvious reasons.
/dev/sda1: UUID: "" TYPE="ext2"
/dev/sda2: UUID: "" TYPE="swap"
/dev/sda3: UUID: "" UUID_SUB="" TYPE="btrfs"
/dev/sda4: UUID: "" UUID_SUB="" TYPE="btrfs"
/dev/loop100: TYPE=squashfs
/dev/loop101: UUID"" TYPE=ext4
/dev/loop102 type=ext4
/dev/mapper/arch_root-image: type ext4
/dev/loop103 TYPE=squashfs
/dev/loop104: UUID TYPE=ext4
/dev/mapper/arch_lib-modules type=ext4
/dev/loop106 type=squashfs
basically rinse repeat all the way to loop 109 & 110 which are both squashfs.
Edit: I just ran pacman -S grub2-bios and it returned warnings stating "could not get filesystem information for /bootmnt, /cowspace, /sfs/root-image, /sfs/lib-modules, /sfs/sur-share, /repo/core/x86_64, /rep/core/any, & /bootmnt (in that order)
Last edited by jallenusn (2012-07-08 23:58:16)

Filesystem ext2/ext3 at Mac OS X

Hi together,
how can i mount a partition with an ext2/ext3 filesystem ?
Thank you and best regards
oelauge

Try using this tool.
(14329)

[svn:sb-asc-redux] 18186: emit versioned uris into a single sorted, consolidated file (bug asc-4141; r=jodyer)

Revision: 18186
Revision: 18186
Author:   [email protected]
Date:     2010-10-15 14:36:17 -0700 (Fri, 15 Oct 2010)
Log Message:
emit versioned uris into a single sorted, consolidated file (bug asc-4141; r=jodyer)
Ticket Links:
    http://bugs.adobe.com/jira/browse/asc-4141
Modified Paths:
    flex/sdk/sandbox/asc-redux/src/java/macromedia/asc/embedding/ScriptCompiler.java

Ext2 redux

Similar Messages

Maybe you are looking for