Every Operating has at least one "file system manager" that allows to store its data and programs into a disk.īut generally, it supports several file systems. The operating, export then syscall to control this new "entities" to programs : "create folder", "create file", "read page of a file", etc. The filesystem also define the notion of "folder", a page containing "pointers" to belonging files, each files maitain also a pointer to its belonging "folder". Thus a file, is a set of "pages" of data, linked in a particular order, each file has a metadata page storing information about the file (ownership, permission, date, size, etc). A page also contains "pointers", to be linked to parent page or child pages. A page can store "data" or "metada", that is information about stored data. This structure is called a "disk partition", containing "file system format" : formatting a disk. Basically, a file system define a structuration of the disk, first partitioning area, then breaking down into logical pages (containing physical blocks or sectors of the disk), some pages having some special funtions, to access the structure. The module that manage a represenation of structured data, that can be stored (via blocks) on a disk, is a "file system manager". The thing that put "meaningness" on those blocks is the Operating system that controls this mainboard and this disk attachement. There is no "file", "folder", "ownership" meaning in a disk, just "blocks of data", stored at a predefined adress. I mean the disk don't have any idea of what the blocks represent. This protocol allow to read or write block (via adressing mechanism) into the disk. The disk is physically attached to the main board, by a bus with standard protocol to control it (SATA protocol in my case). Now I want to spend some time to explain how computers manage their disk. Ok, so a NAS is not a disk, it is a computer with a disk, as our desktop, plus a service to access it. But here, we will discuss (with some expections) only the "file server" service, and in a LAN context. So it is more than a NAS, it could be seen as a "private cloud". It does all this, on your LAN, but is also able to do it for your client, through internet. This DSM propose various installable "paquet", that are actually applications, that propose client/server services : mail server, database server, web server, ftp server, album photo server, streaming multimedia (music and video) server, etc, on top of stored data. This OS is called DSM 6.1, for DiskStaionManager. This computer need an Operating system, and guess what, it is a linux derivative, patched by synology developers. So DS215j is really a computer, with CPU (ARM based), RAM, with a SATA attachement for 2 disks, USB plugs, ethernet plug, etc. So basically this is a client / server pattern, where magia desktop is the client and synology DiskSation is the server (everything is called a "station" in synology, but actually there are "server"). My mageia desktop, is also a computer, also with a disk, but needing extra storage service. So people in the know can skip this first post.Ī NAS (Network attached Storage), is basically a computer, with a disk, offering storage service over a network. After, if we are happy, we could turn this into an "how to" on mageia wiki.įirst, we need to make basics reminders to give a quick cathing-up on background concepts. I still struggling on some points, but I hope to find some help on this thread. Here a testimony, with all the things I learnt during this journey, can also be considred as a short course about NAS, and also a step by step tutorial. Ok, i own a synology DS215j (for Disk Station), got basic features, but never finished a good integration into mageia 5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |