What's the difference on the disk/server level? I mean I watch this video and have exactly the same amount of information as before when not knowing anything about block storage... It's unclear where the differences are.. The differences I was able to take in the end is that "block storage" is greast if you have databases or clouds and file based storage let's you have shares and user access control... What about the physical aspects like disk? When I install mysql on my file storage, does it mean my sql database is then used the wrong way, or is there the possibility of using block storage inside file storage??? Is the block storage on special parts of the harddisks as only from block storage can be booted... What's hypervisor, why even mention it? Nothing gets explained here... Your blocks look like dots inside a box, that's what blocks are to me after watching this video
7:56 block storage is bootable and can be used for file storage as well. What do you mean? Do we build file storage on top of block storage? If so, aren't you comparing apples and oranges?
Yes that is the key information i was seeking .. is file storage just a virtual storage system built on top of a block storage just like an object storage?
My understanding is that these concepts are applicable just in the context of platforms like AWS, Azure, or GCP. So basically, the Block Storage is something like a raw hard drive and the File Storage is something like a hard drive with a file system mounted on top.
Is CDN an object or blob storage? Can you also give some examples in real life, where these storages are used? Also, does BLOCK storage falls under structured data?
I think the prohibition is overstated, but you can think of it like this: a filesystem is itself a hierarchical database. If you run a database on top of another database then it is subject to the whims of the underlying DB. In the case of block storage, the "contract" for multiple access/caching/locking is pretty well defined. Filesystems, however, can vary. Small DBs run happily anywhere. We're talking about big DBs here (many writers, distributed storage). TL;DR: it depends.
NFS, SMB stored in NAS mainly for office files, images used by end users, while block based is for fast access or high IO for Database, clusters or Applications with high transaction where latency is the key .. Network attached vs local/FC/iSCSI will make a big difference in total overall performance, Applications for processing and algorithm where CPU is consumed will reside in local object store side today under SSD . old days in Mirror disks or partitions.. same as OS location
if I want to work on my .DWG file from Autocad, do I have to copy paste to my computer then work on it and upload it again to my NAS after i finished working? or I can work directly from NAS without having to download and upload it every time I work on it?
What are some examples of block storage I can format my devices as? I know for FS there is NTFS and FAT BTRFS. But what systems can I go and get for block storage?
I have a stateless cluster with read only NFS-root, and a cachefilesd to reduce the network traffic. The setup works well for 12 nodes. I was thinking replacing the NFS-root with a block device, like iSCSI, but couldn't find anything good for caching. Any suggestion?
A quick doubt. I see the word "block" being referred in two contexts. Each file when saved is broken into lots of independent parts. I have seen people referring to these small parts of the file as blocks. Secondly you are also using the word block to refer to the storage media i.e. the storage volume that gets mounted. Are both usage correct?
4 minutes into the video and I don't hear a single word explaining the difference, you should just say the different upfront in plain and simple words, really bad presentation
Can I configure a Linux system with multiple keyboards, mouses and monitors so that multiple users can login and share the CPU among themselves? Is it possible to achieve the same in a Windows system?
This guy is the best, always breaks it down in easy to understand terms and diagrams.
This is how explanations should be when coming from actual experience. Bravo!
Prepping to take Sec+ exam and this video presented the concepts perfectly. Thank you
Storage is great. But I am impressed with your writing skills.
Using both of your hands equally in reversed directions is so cool :)
Very clear and simple explained and visualized with the right numbers of words. Thank you so much
What's the difference on the disk/server level? I mean I watch this video and have exactly the same amount of information as before when not knowing anything about block storage... It's unclear where the differences are.. The differences I was able to take in the end is that "block storage" is greast if you have databases or clouds and file based storage let's you have shares and user access control... What about the physical aspects like disk? When I install mysql on my file storage, does it mean my sql database is then used the wrong way, or is there the possibility of using block storage inside file storage??? Is the block storage on special parts of the harddisks as only from block storage can be booted... What's hypervisor, why even mention it? Nothing gets explained here... Your blocks look like dots inside a box, that's what blocks are to me after watching this video
My thoughts exactly.
Did you find any information or resource ? Thanks in advance.
neat and clear explanation. Particularly this guy is awesome . He explain so clearly
Brilliant explanation/comparison of a topic that's hard to understand! Thank you!
you are the best. these explanations are clear and concise.
summary : logical hierarchy of data , chunks of block data
7:56 block storage is bootable and can be used for file storage as well. What do you mean? Do we build file storage on top of block storage? If so, aren't you comparing apples and oranges?
Yes that is the key information i was seeking .. is file storage just a virtual storage system built on top of a block storage just like an object storage?
My understanding is that these concepts are applicable just in the context of platforms like AWS, Azure, or GCP. So basically, the Block Storage is something like a raw hard drive and the File Storage is something like a hard drive with a file system mounted on top.
Is CDN an object or blob storage?
Can you also give some examples in real life, where these storages are used?
Also, does BLOCK storage falls under structured data?
Great, what about an hour or 2 long only on storage theory?
It would be really great to have hour long full coverage lectures. Please try.
lol no. thats what wikipedia is for
Well done, please let's more of this.
Love this explanation. thanks for sharing.
I’m still none the wiser 😂 99 percent went straight over my head
fantastic video but why is the database better suited for block-storage?
I think the prohibition is overstated, but you can think of it like this: a filesystem is itself a hierarchical database. If you run a database on top of another database then it is subject to the whims of the underlying DB. In the case of block storage, the "contract" for multiple access/caching/locking is pretty well defined. Filesystems, however, can vary. Small DBs run happily anywhere. We're talking about big DBs here (many writers, distributed storage).
TL;DR: it depends.
Please make a video of sharing the mounts across the servers.
NFS, SMB stored in NAS mainly for office files, images used by end users, while block based is for fast access or high IO for Database, clusters or Applications with high transaction where latency is the key .. Network attached vs local/FC/iSCSI will make a big difference in total overall performance, Applications for processing and algorithm where CPU is consumed will reside in local object store side today under SSD . old days in Mirror disks or partitions.. same as OS location
Thanks man, that was awesome explanation. You are the best)
if I want to work on my .DWG file from Autocad, do I have to copy paste to my computer then work on it and upload it again to my NAS after i finished working? or I can work directly from NAS without having to download and upload it every time I work on it?
Amazing video fam!
is anyone able to explain the difference between mounting directly to the hypervisor vs mounting to the VSI via a mount point?
very helpful !! thanks !!
What are some examples of block storage I can format my devices as? I know for FS there is NTFS and FAT BTRFS. But what systems can I go and get for block storage?
Thanks
Thank you! great explaination as always.
Great video. Thanks
Thanks!
Someting I don't get is, is "File Storage" not also mounted on block devices such as spinning disks?
I have a stateless cluster with read only NFS-root, and a cachefilesd to reduce the network traffic. The setup works well for 12 nodes. I was thinking replacing the NFS-root with a block device, like iSCSI, but couldn't find anything good for caching. Any suggestion?
excellent 🙂
A quick doubt. I see the word "block" being referred in two contexts. Each file when saved is broken into lots of independent parts. I have seen people referring to these small parts of the file as blocks. Secondly you are also using the word block to refer to the storage media i.e. the storage volume that gets mounted. Are both usage correct?
Exactly. This video is a bit disappointing. Storage and the lingo for storage is confusing.
why cannot boot from file storage (physical reason) ?
Legend
So in short Blocks are used for some apps and file share is used for something like a DAM. If I am not mistaken 😅
4 minutes into the video and I don't hear a single word explaining the difference, you should just say the different upfront in plain and simple words, really bad presentation
👌👌👌
He needs to dumb this down farther ..
IS HE WRITING REVERSE SO WE CAN SEE IT CORRECT ??
Same question
Can I configure a Linux system with multiple keyboards, mouses and monitors so that multiple users can login and share the CPU among themselves? Is it possible to achieve the same in a Windows system?
You can! Check out my video here that explains it - th-cam.com/video/3E0EKUkMEjc/w-d-xo.html